When running virtual machine backups using tools such as VMware Data Recovery (VDR), vSphere Data Protection (VDP), or any third-party backup tool which utilizes Change Block Tracking (CBT) to perform incremental virtual machine backups while running on ESXi 5.x hosts, you may experience one or all of these symptoms:
- Virtual machine backups are much larger than usual.
- Incremental backups take as long and as much space as a full backup.
- Snapshot removal tasks fail because the backup job is still running or the backup window has been exceeded.
This issue occurs because CBT is reset during virtual disk migration using Storage vMotion. This results in the backup tool being unaware which blocks have changed since the last backup. An incremental virtual machine backup is not possible and a full backup is required.
This is a known issue affecting incremental virtual machines backups, which rely on CBT running on ESXi 5.x hosts.
To work around this issue, do not use Storage vMotion or Storage DRS on virtual machines you wish to back up.
To resolve this issue on an affected virtual machine:
- Shut down the virtual machine.
- Remove any existing virtual machine snapshots.
- Disable CBT for the virtual machine. For more information, see Enabling Changed Block Tracking (CBT) on virtual machines (1031873).
- Remove or rename any files ending with the
*-ctk.vmdkfile extension in the virtual machine directory.
- Enable CBT for the virtual machine again.
- Power on the virtual machine.
- Ensure that the virtual machine is not migrated using Storage vMotion or Storage DRS.
In earlier releases of VDDK, virtual machine cold migration (virtual machine powered off) resulted in loss of Changed Block Tracking (CBT) state. In VDDK 5.5 release, if source and destination datastores are accessible to both hosts, CBT state is maintained after cold relocation of virtual machines.
For more information, see the Virtual Disk Development Kit (VDDK) 5.5 Release Notes.