IT41413: VSNAP CLOUD OR ARCHIVE DATA UNDER /OPT/VSNAP-MAINT IS NOT DELETED AS EXPECTED

APAR status

• Closed as program error.

Error description

• The directory /opt/vsnap-maint on the IBM Spectrum Protect Plus
  vSnap server is used during maintenance sessions for cloud or
  archive data and is cleaned up when a maintenance session is
  completed.
  However, some maintenance sessions created in versions prior to
  10.1.10 can be orphaned.
  
  The related data is left behind to occupy space under
  /opt/vsnap-maint.
  The symptoms of this problem are :
  1. left over pending cleanup maintenance sessions well beyond
     the expected retention period seen with the command :
     vsnap cloud maint show
  and
  2. data found under /opt/vsnap-maint timestamped from the same
     moment as the cleanup sessions
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.x
  
  Additional Keywords: SPP, SPPLUS, TS009512933, Cloud, reclaim,
                       reclamation, space, full, usage, filled,
                       empty, occupancy, glacier, cold, IT36640,
                       IT40229
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.3 to 10.1.12           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in IBM Spectrum Protect Plus level     *
  * 10.1.13. Note that this is subject to change at the          *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• The problem occurred because vSnap did not correctly process
  certain types of cloud maint sessions which were created at the
  end of a failed/aborted cloud copy operation. If the
  failed/aborted operation did not fully clean up the cloud
  device, then the device ID was recorded in the maint session.
  During processing of maint sessions, these sessions were always
  skipped and remained in pending state. The problem has been
  resolved by implementing proper checks to verify if the device
  is still active. Once the device is no longer active, the maint
  session is processed further and thus no longer remains stuck in
  pending state.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels