Changed Block Tracking Failures

Valid on Windows.

Symptom:

Virtual machine backups fail and changed block tracking is enabled on the virtual machines.

Solution:

The following table describes environmental conditions that can cause virtual machine backups with changed block tracking enabled to fail:

Condition	Solution
User generated snapshots are present on the virtual machines, and changed block tracking is disabled.	Enable or reset changed block tracking to allow the full backup job to continue. Note: The full backup job continues with used and unused blocks of data from the VMDK files.
The incorrect version of VMware hardware is installed on the virtual machine.	Verify that VMware hardware version 7.0 or later is installed on the virtual machine.
The incorrect version of ESX Server is installed on the virtual machine.	Verify that ESX Server version 4.0 or later is installed on the virtual machine.
The ESX Server system encountered a hard shutdown. Hard shut downs can cause changed block tracking backups to fail.	CA ARCserve Central Host-Based VM Backup automatically enables changed block tracking on the virtual machine.
The ESX Server system encountered a (clean) reboot while the virtual machine was in powered on state.	CA ARCserve Central Host-Based VM Backup automatically enables changed block tracking on the virtual machine.
The virtual machine was moved using Storage vMotion.	CA ARCserve Central Host-Based VM Backup automatically enables changed block tracking on the virtual machine.