IT26385: DISK CONSOLIDATION FAILS AFTER VM BACKUP COMPLETES

APAR status

• Closed as Vendor Solution.

Error description

• VMs require consolidation after backup completion after updating
  Data Protection for VMware to 8.1.6 or 7.1.8.4
  This behavior is only seen when using SAN transport mode and the
  VMDK of the VM being backed up has the following parameter set
  in vmname.vmdk:
  ddb.adapterType = "legacyESX"
  
  This issue is caused by a defect in VMware VDDK 6.7 as described
  in VMware KB https://kb.vmware.com/kb/57865
  
  IBM Spectrum Protect Versions Affected:
  IBM Spectrum Protect for Virtual Environments - Data Protection
  for VMware 8.1.6
  IBM Spectrum Protect for Virtual Environments - Data Protection
  for VMware 7.1.8.4
  The issue is seen on Windows and Linux platforms
  
  Customer/L2 Diagnostics
  
  Review vmware.log from the impacted VM:
  
  AIOGNRC: Failed to open
  '/vmfs/volumes/5acf11a7-f18ec10c-8577-0025b5a100b5/vmname/vmname
  .vmdk' : Failed to lock the file (40003) (0x2013).
  AIOMGR: AIOMgr_OpenWithRetry: Descriptor file
  '/vmfs/volumes/5acf11a7-f18ec10c-8577-0025b5a100b5/vmname/vmname
  .vmdk' locked (try 1)
  AIOGNRC: Failed to open
  '/vmfs/volumes/5acf11a7-f18ec10c-8577-0025b5a100b5/vmname/vmname
  .vmdk' : Failed to lock the file (40003) (0x2013).
  ConsolidateItemComplete: Online consolidation failed for disk
  node 'scsi0:0': Failed to lock the file (5).
  ...
  ConsolidateItemComplete: Online consolidation failed for disk
  node 'scsi0:1': Failed to lock the file (5).
  
  Initial Impact: Medium
  
  Additional Keywords: TSM, Tivoli, Storage, Manager, TS000970838
  

Local fix

• 1. Connect to the ESXi host and browse to the datastore that
  holds the impacted VMs.
  2. Open the vmdk file (vmname.vmdk in previous example) and
  scroll to the 'The Disk Data Base':
  
  ===================================
  # The Disk Data Base
  #DDB
  
  ddb.adapterType = "legacyESX"
  ddb.deletable = "true"
  ddb.encoding = "UTF-8"
  ddb.geometry.cylinders = "1958"
  ddb.geometry.heads = "255"
  ddb.geometry.sectors = "63"
  ddb.longContentID = "4a175b0d38339dcf092e3c9e90d34b30"
  ddb.toolsInstallType = "1"
  ddb.toolsVersion = "10252"
  ddb.uuid = "60 00 C2 99 26 7f dd ff-19 a1 00 3d f9 66 f0 ec"
  ddb.virtualHWVersion = "4"
  ====================================
  
  3. Review the parameter dbb.adapterType. LegacyESX is considered
  as an invalid adapter.
  4. Change this to 'buslogic' or 'lsilogic', depending on what
  the virtual machine guest is using.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• The issue is due to vmware bug: https://kb.vmware.com/kb/57865
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels