Chapter 2: vmPRO Setup and Configuration
vSphere Changed Block Tracking Support
Quantum vmPRO User’s Guide 86
a. Remove all snapshots from the appliance.
b. On the VMware vSphere Client console, enter the following command:
cbt reset <hypervisor> <VM>
VMTransfers
Transferring a VM with Storage vMotion disables CBT.
Standard vMotion (when only the ESX host changes for the VM, but the VM disk stays in the same
storage location) does not disable CBT.
LoadBalancing
Using vMotion on VMs for load balancing during a backup can cause the backup to fail if you do not have
one of the following:
l vmPRO 3.0.1 and newer
l vCenter Server version 5
In these versions, vMotion is disabled on the VMs prior to the start of the backup process.
For vCenter 4.x, you need to configure the VMs so that vMotion does not run during a backup.
MultiplevmPROAppliances
Multiple appliances cannot manage the same VM using CBT.
ActivatingandDeactivatingCBT
Activating or deactivating CBT on a VM triggers the immediate and simultaneous creation and removal
of a VM snapshot. This function is required by the VMware API.
The removal and creation of a snapshot for each VM can be a time-consuming process when activating
or deactivating CBT on multiple VMs.
CBTandRetentionSchedules
During differential disk backups, CBT needs to access data from the flat.vmdk file and the
corresponding database entry. For this reason, the retention schedule for the backup policy does not
initiate partial deletions of full backups. Instead, full backups,differential backups, and associated
database entries are deleted at same time by the same retention schedule.
Configuring CBT on a vmPRO Appliance
Do the following to configure Changed Block Tracking (CBT) on your vmPRO appliance:
Comments to this Manuals