We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Backup

How to Resolve Slow Incremental Backup with VMware

  • Last updated on

If you encounter slow incremental backups when using Changed Block Tracking (CBT), you may need to reset CBT.

Issue

You run a full backup of your virtual machines (VM) running on VMware ESX/ESXi, and then run the backup a second time with only a nominal difference in completion time, and the data size during incremental backup is small and corresponds to the normal size of an incremental backup.

For example, 2TB of data takes ten hours to back up, an incremental backup takes a similar amount of time to complete, and the increase in data size is minimal and corresponds to the actual data change rate.

Cause

CBT is improperly detecting changed disk sectors on the backed up VMs, and returns the range equal to the original data backup size. Barracuda Backup must then read through and analyze all reported sector ranges. This results in the long incremental backup time.

Solution

To resolve this issue, you must manually disable and then re-enable CBT. For more information, refer to the VMware Knowledgebase solution Enabling Changed Block Tracking (CBT) on virtual machines.

 

 

Last updated on