vSphere's Changed Block Tracking (CBT) identifies the disk blocks that have changed on a virtual machine (VM) since the previous backup, allowing the vmPRO appliance to back up VMs at a differential level. Differential-level backups export only the data that has changed since the last full backup, as opposed to backing up the entire VM disk. When you use CBT with SmartMotion backups, both network I/O and backup times are reduced.
Note: Keep in mind that the base disk's modification time is the start of the reset time, while the CBT files have newer modification times.
Figure 1: CBT Cycle
Note: The CBT files are not complete disk images because they contain only the disk's changed data. You cannot access the data in CBT files until you perform a full recovery of these files using the Recover Virtual Machines Wizard.
CBT Considerations
Keep the following in mind when using CBT:
If you are using ESX 4.1, reverting a snapshot resets CBT for that VM.
Resolve the reset
cbt reset <hypervisor> <VM>
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.
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:
vmPRO 3.0.1 and newer
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.
Multiple appliances cannot manage the same VM using CBT.
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.
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.
COMPANY |
SUPPORT |
CONTACT US |
BE CERTAIN ™ |
JOIN US
|
|||
©2015 Quantum Corporation. All Rights Reserved. Last Updated: 8/12/2015 |