IC62853: Q AUDITOCC MAY RETURN INACCURATE OCCUPANCY INFORMATION WITH DEDUPLICATION

IBM Tivoli Storage Manager V6.1 Fix Pack 3 (6.1.3) Server Downloads

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager (TSM) QUERY AUDITOCCUPANCY command
  may return inaccurate occupancy information depending on the
  sequence of backup/identify commands.
  
  Example scenario:
  Node A backs up 20 G of data.
  IDENTIFY DUPLICATES is run against Node A's data, but no
  duplicate chunks are found.
  Node B backs up 20 G of data, 10 G in common with Node A.
  IDENTIFY DUPLICATES is run against Node B's data, and it finds
  the common chunks with Node A's data.
  Storage Pool Reclamation is run.
  
  Q AUDITOCC shows 20G of data used by Node A, and 10G by Node B.
  
  Now, reverse the order of backups:
  Instead of Node A first, then Node B, assume it was Node B
  first, then Node A. In this case Q AUDITOCC shows 10G for Node
  A, and 20G for Node B.
  
  QUERY AUDITOCCUPANCY returns different results depending upon
  who backs up data first.
    Tivoli Storage Manager Versions Affected: 6.1
    Initial Impact: Medium
  

Local fix

• issue a SELECT against the OCCUPANCY table, using the SUM()
  function and GROUP BY as such:
  select node_name,sum( logical_mb ) as "SpaceInMB" from occupancy
  where stgpool_name='POOL1'  or stgpool_name='POOL2' group by
  node_name
  
  add an "OR STGPOOL_NAME='POOL'" clause for each primary pool
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 the QUERY AUDITOCCUPANCY command along       *
  *                 with storage pool deduplication enabled.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.1.3. Note that this is           *
  *                 subject to change at the discretion of IBM.  *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms: AIX, HP-UX, Sun Solaris, 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP