IT04810: FULL BACKUP INSTEAD OF INCREMENTAL WHEN NFS DISK IS USED IN TIVOLI STORAGE MANAGER FOR VIRTUAL ENVIRONMENT

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

• The data mover of Tivoli Storage Manager for Virtual Environment
  do a  Full backup instead of incremental when NFS disk is used.
  
  CBT reset occurred before the Daily ( incremental ) backup.Since
  CBT reset all previous changeIDs , Tivoli storage Manager do a
  Full backup and incremental afterwords.
  
  
  Steps to recreate:
  
  1- Machine must currently have a 6.4.2 B/A client installed and
  Virtual machine data on NFS disk.
  
  2- Separate node name and schedules are defined for Weekly and
  daily backups.
  
  3- After the weekly Full backup on Sunday the next scheduled
  Monday daily backup should be incremental
       but data mover takes as Full backup.
  
  The following entries may be present in the dsmerror.log:
  ----
  
  <Time_stamp> ANS9385W Error returned from VMware vStorage API
  for
               virtual machine 'Test' in vSphere API function
  __ns2__QueryChangedDiskAreas.
               RC=12, Detail message: SOAP 1.1 fault:
               "":ServerFaultCode[no subcode]
               "Error caused by file
  /vmfs/volume/..../Test/Test.vmdk"
               Detail:
  
  <Time_Stamp > ANS9387W An incremental backup for virtual machine
               'Test' is not possible because changed block
  information cannot be
                obtained. A full VM backup is attempted instead.
  
  <Time_Stamp > ANS9384W Unable to get VMware Changed Block
                Tracking(CBT) data for virtual machine 'Test'.
  Full VM backup continues,
                and includes both used and unused areas of the
  disk.
  
  ----
  
  
  
  Tivoli Storage Manager Versions Affected:
  
  Tivoli Storage Manager For Virtual environement 6.4.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All backup-archive client versions 6.3, 6.4 and 7.1 on       *
  * 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 levels 6.3.2.3, 6.3.2.4, 6.4.3,     *
  * and 7.1.2. Note that this is subject to change at the        *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• During full vm backup both used and unused disk areas are backed
  up for disks on NFS datastore.
  

Temporary fix

• 6.3.2.3 for the Linux x86 data mover, and 6.3.2.4 for the
  Windows data movers
  

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

• R63W PSY

     UP

• R64W PSY

     UP

• R71W PSY

     UP

• R63L PSY

     UP

• R64L PSY

     UP

• R71L PSY

     UP