IT25132: BACKUP FAILS WITH ANS4200E WHEN THE VM INCLUDES A RDM DISK > VMMAXVIRTUALDISK

APAR status

• Closed as program error.

Error description

• The backup of VM's with RDM disks will fail in the following
  scenario:
  
  * The datamover has the following options set:
     VMDATASTORETHRESHOLD xx
     VMMAXVIRTUALDISK Y
  
  * The RDM disk is larger than the VMMAXVIRTUALDISK value
  
  The backup will fail with following error:
  ANS4200E The virtual machine 'vmname' could not be backed up
  because the data usage of datastore 'datastore1' exceeded the
  datastore threshold of xx percent.
  
  
  This should not happen because the manual states:
  "Independent disks are not checked during space verification
  processing because a snapshot of these disks does not use any
  VMware datastore space."
  
  When the disk is smaller than the VMMAXVIRTUALDISK value, the
  backup completes fine.
  
  IBM Spectrum Protect Versions Affected:
  IBM Spectrum Protect for Virtual Environments - Data Protection
  for VMware 7.1 and 8.1 on Windows and Linux
  
  Customer/L2 Diagnostics:
  
  Review a service trace of the VM backup:
  
  vmbackvcb.cpp       (2074): vmVcbGetVMList: VM entry(1)
  vmbackvcb.cpp       (2075): vmVcbGetVMList:    VM
  vmName='vmname'
  vmbackvcb.cpp       (2076): vmVcbGetVMList:    VM
  DisplayName='vmname'
  vmbackvcb.cpp       (2077): vmVcbGetVMList:    VM
  hostAddress='localhost.localdomain'
  vmbackvcb.cpp       (2078): vmVcbGetVMList:    VM ipAddress=''
  vmbackvcb.cpp       (2079): vmVcbGetVMList:    VM
  hostSystem='esxi.hostname'
  vmbackvcb.cpp       (2080): vmVcbGetVMList:    VM
  datacenter='DC_name'
  vmbackvcb.cpp       (2081): vmVcbGetVMList:    VM guestFolder=''
  vmbackvcb.cpp       (2082): vmVcbGetVMList:    VM
  guestFullName='CentOS 4/5/6 (32-bit)'
  vmbackvcb.cpp       (2083): vmVcbGetVMList:    VM
  moref='vm-xxxx'
  vmbackvcb.cpp       (2084): vmVcbGetVMList:    VM
  guestState='notRunning'
  vmbackvcb.cpp       (2085): vmVcbGetVMList:    VM
  uuid='xxxxxxxx-yyyy-zzzz-aaaa-bbbbbbbbbbbb'
  vmbackvcb.cpp       (2097): vmVcbGetVMList: VM VMDK[1] Label
  (UTF-8)='Hard disk 1'
  vmbackvcb.cpp       (2098): vmVcbGetVMList: VM VMDK[1] Label
  ='Hard disk 1' (Hard Disk 1)
  vmbackvcb.cpp       (2099): vmVcbGetVMList: VM VMDK[1] Name
  ='[datastore1] vmname/vmname.vmdk'
  vmbackvcb.cpp       (2100): vmVcbGetVMList: VM VMDK[1]
  Status='0'
  vmbackvcb.cpp       (2097): vmVcbGetVMList: VM VMDK[2] Label
  (UTF-8)='Hard disk 2'
  vmbackvcb.cpp       (2098): vmVcbGetVMList: VM VMDK[2] Label
  ='Hard disk 2' (Hard Disk 2)
  vmbackvcb.cpp       (2099): vmVcbGetVMList: VM VMDK[2] Name
  ='[datastore1] vmname/vmname_1.vmdk'
  vmbackvcb.cpp       (2100): vmVcbGetVMList: VM VMDK[2]
  Status='16'
  
  Status='16' means "disk is excluded because it's larger than the
  max size we can support"(VMSELECTED_VMDK_MAXIMUM)
  Later the result of the threshold check is skipped only if
  status of disks VMSELECTED_INDEPENDENT or VMSELECTED_PRDM.
  In this case, this check is not skipped because we got
  VMSELECTED_VMDK_MAXIMUM.
  
  vmbackvddk.cpp      (18946): CheckThresholdExceeded(): free
  space = 123456789, capacity = 1234567890.
  vmbackvddk.cpp      (18947): CheckThresholdExceeded(): datastore
  usage = zz.zz%, threshold = xx%.
  vmbackvddk.cpp      (18955): <=========
  CheckThresholdExceeded(): Exiting, rc = 6716
  vmbackcommon.cpp    (4693): ANS4200E The virtual machine
  'vmname' could not be backed up because the data usage of
  datastore 'datastore1' exceeded the datastore threshold of xx
  percent.
  
  The failure seen is a combination of options VMMAXVIRTUALDISK Y,
  VMDATASTORETHRESHOLD XX and size of independent disk that
  exceeds YTB.
  
  Initial Impact: Medium
  
  Additional Keywords: TSM, Tivoli, Storage, Manager, TDP4VE,
  TS000847835
  

Local fix

• Set VMMAXVIRTUALDISK to a value larger than the RDM disk
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Data Protection for VMware Data Mover  versions 7.1.0-7.1.8  *
  * and 8.1.0-8.1.6  running on all Windows x64 and Linux x86    *
  * platforms.                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed                                                  *
  * in Data Protection for VMware Data Mover version 8.1.7 on    *
  * all Windows x64 and Linux x86 platforms.                     *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• After the fix  backup VM command of RDM disk that is larger than
  the VMMAXVIRTUALDISK value and with options
  set VMDATASTORETHRESHOLD xx, VMMAXVIRTUALDISK
  Y(VMDATASTORETHRESHOLD should exceed for target disk..)
  works as expected.
  

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

• dsmc
  

Fix information

• Fixed component name

  TSM FOR VE DP V

• Fixed component ID

  5725TVEVM

Applicable component levels