IT12066: CLIENT CRASH DURING VM BACKUPS WHEN LENGTH OF DATAMOVER NODE, DATACENTER NAME,DATACENTER NODE,GUEST OS IS LONGER THAN 139 CHAR

IBM Spectrum Protect client 7.1.4.x interim fix downloads

APAR status

• Closed as program error.

Error description

• During a VM backup, the Backup/Archive client can crash if the
  combined length of datamover nodename + datacenter name +
  datacenter nodename + guest OS name is longer than 139
  characters.
  The Guest name is the full OS name as seen by VMware.
  Example: "Microsoft Windows Server 2003 Standard (32-bit)"
  7.1.3.0 Stack Trace:
  ntdll!RtlFreeHeap+0xd0
  kernel32!HeapFree+0xa
  msvcr110!free+0x1c
  tsmapi64!dsmFree+0x7c
  [d:\auto\official\ba713\common\mem\dsmem.cpp @ 613]
  tsmapi64!tsmEndSendObjEx+0x6c9
  [d:\auto\official\ba713\api\common\dsmsend.cpp @ 2617]
  tsmapi64!dsmEndSendObjEx+0x78
  [d:\auto\official\ba713\api\common\dsmsend.cpp @ 2374]
  dsmc!vmAPISendData::termSendData+0xc7
  [d:\auto\official\ba713\common\vm\vmapisenddata.cpp @ 2272]
  dsmc!VmCreateDiskGroup+0x215
  [d:\auto\official\ba713\common\vm\vmcdfgrp.cpp @ 784]
  dsmc!VmSendData+0x1074
  [d:\auto\official\ba713\common\vm\vmbackvddk.cpp @ 5511]
  dsmc!vmVddkBackupVM+0x2aa7
  [d:\auto\official\ba713\common\vm\vmbackvddk.cpp @ 8056]
  dsmc!vmBackupVM+0x61
  [d:\auto\official\ba713\common\ba\vmback.cpp @ 4050]
  dsmc!tlVMSend+0x136 [d:\auto\official\ba713\common\ba\txncon.cpp
  @ 1919]
  dsmc!DccTxnConsumer::HandleQueue+0x766
  [d:\auto\official\ba713\common\ba\bacontrl.cpp @ 3161]
  dsmc!DccTxnConsumer::Run+0x6a2
  [d:\auto\official\ba713\common\ba\bacontrl.cpp @ 2789]
  dsmc!DccTxnConsumer::DoThread+0xc4
  [d:\auto\official\ba713\common\ba\bacontrl.cpp @ 3679]
  dsmc!startThread2+0x81
  [d:\auto\official\ba713\common\thrd\thrdmgr.cpp @ 1566]
  dsmc!startThread+0x9
  [d:\auto\official\ba713\common\thrd\thrdmgr.cpp @ 1527]
  Initial Impact: Medium
  Version affected: 6.3, 6.4, 7.1
  Platforms affected: Windows & Linux
  

Local fix

• 1- Rename the datamover node on the server.
  2- Update the datamover options files to use the new nodename.
  3- Remove and create the CAD/Agent/Scheduler services to use the
  new nodename.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Tivoli Storage Manager for Virtual Environments Data         *
  * Protection for VMware version 7.1 running on all Microsoft   *
  * Windows x64 and Linux x86_64 platforms                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * This issue is projected to be fixed in the Tivoli Storage    *
  * Manager Client on Windows x64 and Linux x86_64  in level     *
  * 7.1.6                                                        *
  * Note 1: The Tivoli Storage Manager (TSM) Client is a         *
  * prerequisite to using the Data Protection for VMware. In     *
  * Data Protection for VMware environments, the TSM Client is   *
  * also known as the data mover.                                *
  * Note 2: This is subject to change at the discretion of IBM.  *
  ****************************************************************
  

Problem conclusion

• The client now correctly handles long datamover, datacenter and
  guest os names.
  Note: if the crash occurred on a pre-fixing level, the vm
  filespace may have incorrect data storred on server and cause
  unpredicted errors during subsequent backups. To avoid this,
  that vm filespace should be manually removed from server.
  

Temporary fix

• A fix for this problem is currently targeted for interim fix
  7.1.4.4.  Until the interim fix is actually available, this
  information is subject to change at the discretion of IBM.
  The fix will limit the length of datamover, datacenter and guest
  os names.
  Note: if the crash occurred on a pre-fixing level, the vm
  filespace may have incorrect data storred on server and cause
  unpredicted errors during subsequent backups. To avoid this,
  that vm filespace should be manually removed from server.
  

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 dsm
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R71W PSY

     UP

• R71L PSY

     UP