IT25232: MOVE CONTAINER MIGHT NOT START AUTOMATICALLY FOR STORAGE POOLS THAT ARE NOT SOURCE FOR PROTECT STGPOOL

8.1.6.000-IBM-SPSRV-AIX
8.1.6.000-IBM-SPSRV-Linuxppc64le
8.1.6.000-IBM-SPSRV-Linuxs390x
8.1.6.000-IBM-SPSRV-Linuxx86_64
8.1.6.000-IBM-SPSRV-WindowsX64
8.1.6.000-IBM-SPOC-AIX
8.1.6.000-IBM-SPOC-LinuxPPC64le
8.1.6.000-IBM-SPOC-Linuxs390x
8.1.6.000-IBM-SPOC-Linuxx86_64
8.1.6.000-IBM-SPOC-WindowsX64
8.1.6.000-IBM-SPCMS-Linuxx86_64
8.1.6.000-IBM-SPCMS-WindowsI32
8.1.6.000-IBM-SPCMS-WindowsX64
8.1.6.100-IBM-SPSRV-Linuxppc64le
8.1.6.100-IBM-SPSRV-AIX
8.1.6.100-IBM-SPSRV-Linuxs390x
8.1.6.100-IBM-SPSRV-Linuxx86_64
8.1.6.100-IBM-SPSRV-WindowsX64
IBM Spectrum Protect Server V8.1 Fix Pack 6 (V8.1.6) Downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads

APAR status

• Closed as program error.

Error description

• The IBM Spectrum Protect server might not start automatic
  defragmentation via MOVE CONTAINER on a storage pool that has
  never been used as a source for PROTECT STGPOOL.
  For details on how to confirm the APAR condition see L2
  Diagnostics below.
  
  L2 Diagnostics:
  If it has been confirmed that the storage pool never has been
  used as a source for PROTECT STGPOOL command, a trace with
  traceflags SDCNTR SDDEFRAG, run for 3 hours, is required to
  verify the APAR condition is met.
  
  If this trace point is seen, and both conditions are true,
   [RecomputeTriggersForDefrag]:PoolID X, FsSpaceLow: True,
  CntrSpaceLow True
  
  and if a dedup container is seen in this trace point in
  GetContainersForDefrag with a "seconds since last written" of
  any value
   [GetContainersForDefrag]:Seconds since container last written:
  [any number]
  
  or if a non-dedup container is seen in this trace point with a
  "seconds since last written" greater than or equal to 1814400
  [GetContainersForDefrag]:Seconds since container last written:
   [any number >= 1814400]
  
  but this trace point is NOT seen following it:
  "Adding cntr <cntrid> to list"
  
  or if this trace point is seen, and only one or the other is
  true:
  [RecomputeTriggersForDefrag]:PoolID X, FsSpaceLow: <True/False>,
  CntrSpaceLow <True/False>
  
  and if a dedup container is seen in this trace point in
  GetContainersForDefrag with a "seconds since last written"
  greater than or equal to 604800
  [GetContainersForDefrag]:Seconds since container last written:
  [any number >= 604800]
  
  or if a non-dedup container is seen in this trace point with a
  "seconds since last written" greater than or equal to 1814400
  
  but this trace point is NOT seen following it:
  "Adding cntr <cntrid> to list"
  
  Then this APAR is confirmed.
  
  You can tell if a given container in the trace is a dedup or a
  non-dedup container by looking for the next following trace
  point:
  [SdFreeContainerDesc]:Enter: descP xxx, cntrId xxx, container
  file [container name]...
  A dedup container will have an extension of ".dcf", and a
  non-dedup container will have an extension of ".ncf"
  
    IBM Spectrum Protect Versions Affected: 8.1.5
    Initial Impact: Medium
    Additional Keywords: TSM container dedup defrag TS000846156
  

Local fix

• manually release space following the instructions from :
  
  "Releasing file system space in an IBM Spectrum Protect
  environment"
  http://www-01.ibm.com/support/docview.wss?uid=swg27050411
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 8.1.6.                        *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms for reported release:  AIX, Linux, and
  Windows.
  Platforms fixed:  AIX, Linux, and Windows.
  

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

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels