IC95198: TIVOLI STORAGE MANAGER CLIENT 6.4 MAY CRASH WHEN RESTORING VM THAT HAS INDEPENDENT DISKS.

IBM Tivoli Storage Manager (TSM) client 7.1.0.x interim fix downloads
IBM Tivoli Storage Manager (TSM) Client 7.1.1 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• Tivoli Storage Manager Client 6.4 may crash when restoring VM
  that has independent disks.
  
  Problem Description:
  When doing "RESTORE VM" using the Tivoli Storage Manager Client
  6.4, dsmagent.exe may crash.
  
  The problem can happen only when the following conditions are
  met:
  - The target VM has independent disks.
  - The backup VM was taken with
  "-vmprocessvmwithindependent=yes" by Tivoli Storage Manager
  Client 6.3.
  
  Here is the call stack from the crash dump.
  ----
    *** Stack trace for last set context - .thread/.cxr resets it
   # Call Site
  00 msvcr100!memmove+0x120
  01
  dsmagent!std::basic_string<char,std::char_traits<char>,std::allo
  cator<char> >::assign+0xd4
  02 dsmagent!vmRestoreAllDataToNewVM+0x893
  03 dsmagent!LegacyRestoreVM+0x2e1
  04 dsmagent!vmVddkRestoreVM+0x1e8
  05 dsmagent!vmRestoreVM+0x63
  06 dsmagent!DoVMRestore+0x5b
  07 dsmagent!DccRestoreConsumer::ProcessRequest+0x104d
  08 dsmagent!DccRestoreConsumer::HandleQueue+0x584
  09 dsmagent!DccRestoreConsumer::Run+0x167
  0a dsmagent!startThread2+0x81
  0b dsmagent!startThread+0x9
  0c msvcr100!endthreadex+0x43
  0d msvcr100!endthreadex+0xdf
  0e kernel32!BaseThreadInitThunk+0xd
  0f ntdll!RtlUserThreadStart+0x1d
  ---
  
  Tivoli Storage Manager Versions affected:
  Tivoli Storage Manager Client 6.4.0 on all supported platforms.
  
  Additional Keywords:
  Independent disk, RDM disk, VMware
  
  Additional L2 info:
  The problem is that Tivoli Storage Manager 6.4 client does not
  properly exclude independent disks from restore.  The issue
  occurs because in 6.3 the exclude process for independent disks
  was different: in 6.4 a selected status for each disk was
  added, which indicates if the disk was excluded by the user,
  due to being rdm/independent.
  
  Initial Impact:
  High
  

Local fix

• Use "-vmdk" option to manually exclude independent disks during
  restore.
  

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

• DSMAGENT
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R64L PSY

     UP

• R64W PSY

     UP