IC96021: TIVOLI STORAGE MANAGER SNAPDIFF SNAPSHOT(S) CAN REMAIN IF THE INCREMENTAL SNAPDIFF BACKUP IS CANCELLED

IBM Tivoli Storage Manager (TSM) Client 7.1.1 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• There should never be more than one Tivoli Storage Manager
  snapdiff created snapshot.
  If the entire snapdiff backup fails, two snapshots are
  left on the volume - the base snapshot which is registered on
  the server
  and the diff snapshot that the backup which failed created.
  
  The next backup should use the same registered base snapshot,
  create a new diff snapshot, and, assuming the backup completes,
  delete the old base and register the current diff on the server
  to be the base in the next backup.
  
  What happens is that the diff snapshot created by the backup
  which failed didn't get deleted. Since it isn't registered as
  the new base
  it will never be used by a future backup and therefore will
  never be deleted.
  
  
  This can be recreated by following steps;
  
  Run an INCREMENTAL -SNAPDIFF command a few times from the dsmc,
  and cancel the backup in the middle with CTRL+C.
  
  The backup will stop, and the snapshot created during each
  backup will
  remain on the NetApp.
  
  similarly, when the backup terminates due to a severe error
  (client returns 12),
  the issue occurs.
  
  
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Client versions 6.1, 6.2, 6.3 and 6.4 on
  AIX, Linux and Windows
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  TSM zz61 zz62 zz63 zz64  snapdiff snapshot delete netapp
  

Local fix

• Delete all snapshots newer than the oldest Tivoli Storage
  Manager created snapshot. That would guarantee that the
  remaining
  Tivoli Storage Manager snapshot would be used as the base in the
  next snapdiff backup regardless of whether or not it is
  registered as the base.
  
  If the registered base doesn't exist (was deleted), the most
  recent snapshot older than the registered base will be selected
  as the base for the backup.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Version 6.1.0 - 7.1.0 backup-archive clients *
  *                 running on Microsoft Windows, AIX and Linux. *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.4.2 and 7.1.1. Note that this is *
  *                 subject to change at the discretion of IBM.  *
  ****************************************************************
  *
  

Problem conclusion

• After installing the fixing code the client will remove all
  snapshots created by TSM except the one which is currently
  registered on the TSM server as the base snapshot.
  

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:

Modules/Macros

• DSMC
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R64A PSY

     UP

• R64L PSY

     UP

• R64W PSY

     UP