IT12585: INVENTORY EXPIRATION PROCESSING DOES NOT LOG SKIPPED OBJECTS

7.1.7.000-TIV-TSMSRV-SolarisSPARC
7.1.7.000-TIV-TSMSRV-Linuxs390x
7.1.7.000-TIV-TSMSRV-Linuxppc64
7.1.7.000-TIV-TSMSRV-WIN
7.1.7.000-TIV-TSMSRV-Linuxx86_64
7.1.7.000-TIV-TSMSRV-HP-UX
7.1.7.000-TIV-TSMSRV-AIX
IBM Spectrum Protect Server V7.1 Fix Pack 7 (7.1.7.000) Downloads

APAR status

• Closed as program error.

Error description

• Inventory expiration will not delete expired objects belonging
  to a client node which replicates to another server if those
  objects have not yet been replicated. These not yet replicated
  objects are skipped by expiration without any externalized
  indication. Expiration statistics only show the number of
  objects that were examined, deleted, retried, and failed. A
  count of files that were skipped (eligible for deletion but not
  deleted during expiration) is missing from the expire inventory
  statistics. The ending expiration processing statistics should
  include a number of objects skipped and the associated message
  details should indicate that lack of the objects being
  replicated is the reason for them having been skipped.
  
  Example from Inventory file expiration processing for a
  replicated VM "filespace" :
  11/18/2015 13:42:25      ANR0166I Inventory file expiration
  finished processing for
                            node NODE_NAME, filespace
  \\FILESPACE_NAME, copygroup
                            BACKUP and object type FILE with
  processing
                            statistics: examined 30, deleted 0,
  retrying 0, and
                            failed 0.
  
  Note that in this case 30 files are examined, none are deleted
  and 0 have failed. This in turn lead to excessive or unexpected
  occupancies for the node since expected to expire was not being
  deleted.
  
  Lack of messaging required expiration process tracing to
  determine why expiration is not deleting examined objects marked
  for deletion. TSM server tracing with flags SESSION IMDEL IMEXP
  shows the following message during inventory expiration:
  
  14:23:40.897 [195][imdmgr.c][5098][ExpireBackupData]:8693210953
  has not been replicated but filespace has. Skipping delete for
  now
  
  Tivoli Storage Manager Versions Affected:
  TSM Server 7.1.x; Platform Independent
  
  Customer/L2 Diagnostics:
  
  Initial Impact:
  Moderate
  
  Additional Keywords:
  Inventory expiration, expiration, expire inventory, occupancy,
  logical space occupied, physical space occupied, repl node,
  replicated, replicate, ANR0166I, client replication,
  replication, node replication, inflated, expire immediately,
  skipping, TSM Spectrum Protect
  

Local fix

• Replicate the node data over to your configured target server,
  or disable replication for this node.
  Depending on the route chosen, Issue either:
  REPLICATE NODE <NODE_NAME>
  REMOVE REPLNODE <NODE_NAME>
  

Problem summary

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

Problem conclusion

• This problem was fixed.
  Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows.
  
  The following messages have been updated to include a skipped
  count:
  ANR0166I, ANR0812I, ANR0813I, and ANR0837I
  The status from QUERY PROCESS for inventory expiration has also
  been updated
  with a skipped count.
  
  The skipped count represents the number of objects that were not
  able to be
  deleted due to using dissimilar policy for replication.  Check
  the individual
  skipped counts in the ANR0166I to see what needs to be
  replicated to allow
  inventory expiration to delete the files.
  

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

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP