IT02150: SNAPDIFF CHANGE LOG MIGHT NOT INITIALIZE PROPERLY DESPITE AN ANS2327I MESSAGE BEING LOGGED

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

APAR status

• Closed as program error.

Error description

• When backing up a NAS volume using Snapshot difference
  incremental backup for the first time, the following message
  appears at the beginning of the backup :
  
  ANS2327I Creating Snapshot Differential Change Log
  
  This also happens if the option createnewbase=yes is used.
  This means a snapshot differences change log database was
  created and it will be used for the next incremental snapdiff
  operation.
  If an error happens during the first backup, the change log is
  not initialized and the next snapdiff backup will also be a full
  instead of being a incremental snapdiff.
  
  
  Tivoli Storage Manager Versions Affected:   7.1
  
  Customer/L2 Diagnostics :
  
  A trace with flags  'SERVICE CACHEDB BTREEDB SNAPDIFFDB
  SNAPSHOT' shows the following at end of the first backup :
  
  txncon.cpp(2369): tlPostProcessTxnSpec(): Completed snapdiff
  full incremental backup, number of failures=2.
  
  Initial Impact: Low
  
  Additional Keywords:
  TSM persistent nas netapp snapshot
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Backup-archive client version 7.1.0 running  *
  *                 on the following platforms:                  *
  *                 - all Windows                                *
  *                 - AIX 64-bit                                 *
  *                 - Linux x86/86_64                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 7.1.1. Note that this is subject    *
  *                 to change at the discretion of IBM.          *
  ****************************************************************
  *
  

Problem conclusion

• The problem described in this APAR has been fixed so that it
  no longer occurs.
  

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

• R71A PSY

     UP

• R71L PSY

     UP

• R71W PSY

     UP