IT05014: CLIENT MAY CRASH DURING CLIENT-SIDE DEDUPLICATION BACKUP WITH DEDUP-CACHE ENABLED

IBM Tivoli Storage Manager (TSM) Client 7.1.2 Downloads and READMEs
IBM Tivoli Storage Manager Client 6.4.3 Downloads and READMEs
IBM Tivoli Storage Manager (TSM) client 6.3.2.x interim fix downloads - EOL

APAR status

• Closed as program error.

Error description

• During client-side deduplication backup the Tivoli Storage
  Manager client may crash if the dedup-cache is enabled.
  
  The crash may occur due to multi-threading timing issue between
  two consumer threads accessing the Tivoli Storage Manager
  Client's dedup-cache database.
  
  The dsmcrash.log shows the following errors:
  
  ****************
  dsmc.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION)
  at 00000000F5BC6890
  
  Register dump:
  
  Crash dump successfully written to file 'C:\Program
  Files\Tivoli\TSM\baclient\dsmcrash.dmp'
  
  Stack Trace:
  TSMAPI64.dll, dsmPingEx()+708736 bytes
  TSMAPI64.dll, dsmPingEx()+2199977 bytes
  TSMAPI64.dll, tsmEndTxnEx()+985 bytes
  TSMAPI64.dll, dsmEndTxnEx()+90 bytes
  dsmc.exe, cXMLiterator::cXMLiterator()+2632862 bytes
  dsmc.exe, cXMLiterator::cXMLiterator()+2322382 bytes
  dsmc.exe, cXMLiterator::cXMLiterator()+2334089 bytes
  dsmc.exe, cXMLiterator::cXMLiterator()+2382821 bytes
  ...
  dsmc.exe, cXMLiterator::cXMLiterator()+1661713 bytes
  dsmc.exe, cXMLiterator::cXMLiterator()+1661769 bytes
  MSVCR110.dll, beginthreadex()+263 bytes
  MSVCR110.dll, endthreadex()+402 bytes
  kernel32.dll, BaseThreadInitThunk()+13 bytes
  ntdll.dll, RtlUserThreadStart()+33 bytes
  
  Customer/L2 diagnostic:
  
  Client's dump stack trace shows:
  
  tsmapi64.dll!GetEight(unsigned char * eightPtr)
  tsmapi64.dll!DedupDB::CheckDbSize()
  tsmapi64.dll!tsmEndTxnEx(tsmEndTxnExIn_t * tsmEndTxnExInP,
  tsmEndTxnExOut_t * tsmEndTxnExOutP)
  tsmapi64.dll!dsmEndTxnEx(dsmEndTxnExIn_t * dsmEndTxnExInP,
  dsmEndTxnExOut_t * dsmEndTxnExOutP)
  dsmc.exe!vmAPISendData::endTxn(unsigned short * reasonP,
  unsigned __int64 * groupLeaderObjIdP)
  dsmc.exe!VmProcessExtent(VixDiskLibHandleStruct * hDisk,
  DiskChangeBlockInfo * diskChangeBlockInfoP,
  const DiskChange & diskChange, unsigned long diskNum,
  VolumeControlHandle_def * pVolCtlHandleP, wchar_t *
  vmName, vmProcessExtentData_t * vmProcessExtentDataP, unsigned
  long numOfExtents, int bWantCDF,
  vmBackupData_t * vmBackupDataP, unsigned long *
  datsNumberExtent)
  dsmc.exe!VmSendData(vmBackupData_t * vmBackupDataP, int
  bWantCDF, nfVmObjInfoVM_t * nfVmObjInfoVmP)
  dsmc.exe!vmVddkBackupVM(vmData * vmDataP)
  dsmc.exe!vmBackupVM(vmData * vmDataP)
  dsmc.exe!tlVMSend(txnConsumerObject_t * txnConObjP, txnSpec_t *
  txnSpecP, DccBackupController * baCP)
  dsmc.exe!DccTxnConsumer::HandleQueue()
  dsmc.exe!DccTxnConsumer::Run(void * argP)
  dsmc.exe!DccTxnConsumer::DoThread(void * argP)
  dsmc.exe!startThread2(Threadstart * startInfoP)
  dsmc.exe!startThread(Threadstart * startInfoP)
  msvcr110.dll!_callthreadstartex()
  msvcr110.dll!_threadstartex(void * ptd)
  
  Tivoli Storage Manager Versions Affected:
  All supported Tivoli Storage Manager Client on all supported
  platforms.
  
  Initial Impact:
  Medium
  
  Additional Keywords:
  crash dmp dump hang hung failure fail dedup deduplication zz62
  zz63 zz64 zz71
  

Local fix

• Delete or rename the cache db file generated by the client under
  the 'DEDUPCACHEPath' folder.
  The dedup cache file will be generated again by the client.
  OR
  Disable the client's deduplication cache DB setting in the
  dsm.opt file the option:
  ENABLEDEDUPCache NO
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All backup-archive client versions 6.1, 6.2, 6.3, 6.4 and    *
  * 7.1 on all platforms.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in levels 6.3.2.3, 6.4.3 and 7.1.2.    *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• The problem has been fixed and no longer occurs.
  

Temporary fix

• 6.3.2.3 for UNIX and Linux clients
  

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

• dsmagent
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R71W PSY

     UP

• R71L PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71M PSY

     UP

• R71S PSY

     UP

• R64W PSY

     UP

• R64L PSY

     UP

• R64A PSY

     UP

• R64H PSY

     UP

• R64M PSY

     UP

• R64S PSY

     UP

• R63W PSY

     UP

• R63L PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63M PSY

     UP

• R63S PSY

     UP