IC93071: FULL VM BACKUPS FAIL WITH APPLICATION PROTECTION ENABLED

IBM Tivoli Storage Manager (TSM) Client 7.1.0 Downloads

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager for Virtual Environments running a
  backup with mode set to IFFULL and Application Protection
  enabled for a virtual machine can result in failures due to how
  Application Protection handles failures it encounters with
  change block tracking. During backup the following is
  seen:
   ANS9365E VMware vStorage API error for virtual machine
   '{VMName}'.
     TSM function name : __ns2__TerminateProcessInGuest
     TSM file          : vmvisdk.cpp (1661)
     API return code   : 12
     API error message : SOAP 1.1 fault: "":ServerFaultCode[no
     subcode]
    "The guest process (pid) was not found."
     Detail:
  
   ANS9431E IBM Tivoli Storage Manager application protection
   failed to thaw VSS writers on virtual machine '{VMName}'. See
   the TSM error log for more details.
  
   ANS4174E Full VM backup of VMware Virtual Machine '{VMName}'
   failed with RC=115 mode=Incremental Forever - Full
  
  The trace shows where the function that causes the ANS9365E has
  already frozen the writers and been terminated:
   06/05/2013 16:27:35.598 [004628] [4160] : vmvisdk.cpp
   (7091): Started
   C:\Users\TEMP\AppData\Local\Temp\TSM\DummyBAProxy.exe
   sucessfully, PID = 4072
   06/05/2013 16:27:56.799 [004628] [4160] : vmvisdk.cpp
   (7195): visdkTerminateProcessInGuest(): ENTER: pid = 4072, name
   = ''
   06/05/2013 16:27:56.799 [004628] [4160] : vmvisdk.cpp
   (7263): visdkTerminateProcessInGuest(): Terminating process
   4072 06/05/2013 16:27:57.002 [004628] [4160] : vmvisdk.cpp
   (7278): visdkTerminateProcessInGuest(): Process 4072
   sucessfully terminated
   06/05/2013 16:27:57.002 [004628] [4160] : vmvisdk.cpp
   (7281): visdkTerminateProcessInGuest(): EXIT, rc = 0
  
  We then see where the CBT error is reported:
   06/05/2013 16:28:05.332 [004628] [4160]
   ..\..\common\vm\vmbackvddk.cpp(11874): VmCheckCBTSupport():
   Error -1 getting change block tracking data for VM
   '{VMNAME}'.  Reset CBT and retry.
  
  The backup then attempts to reset CBT and tries again which
  results in the failure:
   06/05/2013 16:31:38.369 [004628] [4160] :
   ..\..\common\vm\vmbackvddk.cpp(10345):
   vmVddkFullVMPrePareToOpenVMDKs: Taking snapshot 'TSM-VM
   Snapshot'
   06/05/2013 16:31:38.369 [004628] [4160] :
   ..\..\common\vm\vmbackvddk.cpp(10349):
   vmVddkFullVMPrePareToOpenVMDKs: Thawing writers...
   06/05/2013 16:31:38.369 [004628] [4160] :
   ..\..\common\vm\acm.cpp( 837): ACM::Thaw(): ENTER
   06/05/2013 16:31:38.369 [004628] [4160] :
   ..\..\common\vm\wsops.cpp( 299):
   WsGuestOperations::TerminateProcess(): ENTER
   06/05/2013 16:31:38.369 [004628] [4160] : vmvisdk.cpp
   (7195): visdkTerminateProcessInGuest(): ENTER: pid = 4072, name
   = ''
   06/05/2013 16:31:38.369 [004628] [4160] : vmvisdk.cpp
   (7263): visdkTerminateProcessInGuest(): Terminating process
   4072 06/05/2013 16:31:38.587 [004628] [4160] : vmvisdk.cpp
   (7270): visdkTerminateProcessInGuest():
   __ns2__TerminateProcessInGuest failed, soapRet = 12
  
  Tivoli Storage Manager Versions Affected: All Tivoli
  Storage Manager for Virtual Environments with Application
  Protection enabled
  
  Initial Impact: Medium
  
  Additional Keywords: tdpve vm
  

Local fix

• Run a backup cycle (iffull/ifincr) without application
  protection to reset the block tracking
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Backup-archive client version 6.4 running    *
  *                 on all Microsoft Windows and Linux           *
  *                 platforms.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 6.4.2. Note that until the fixing   *
  *                 level is available, this information is      *
  *                 subject to change at the discretion of IBM.  *
  ****************************************************************
  *
  

Problem conclusion

• The problem 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

• DSM
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R64L PSY

     UP

• R64W PSY

     UP