The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Changed Block Tracking is reset after a storage vMotion operation in vSphere 5.x (2048201)
- Virtual machine backups are 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 exceeds
- CBT files grow large, although there are no major changes in the virtual machine
This is a known issue affecting ESXi 5.0.
This issue is resolved in:
To work around this issue, do not use Storage vMotion or Storage DRS on virtual machines to backup.
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.
For more information, see the Virtual Disk Development Kit (VDDK) 5.5 Release Notes.
Note: For related information, see When Changed Block Tracking is enabled in VMware vSphere 5.x, vMotion migration fails with error: The source detected that the destination failed to resume (2086670)
To be alerted when this article is updated, click Subscribe to Document in the Actions box.
- When Changed Block Tracking is enabled in VMware vSphere 5.x, vMotion migration fails with error: The source detected that the destination failed to resume (2086670)
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.