VMware
If a Veeam backup job gets interrupted part way through it, you can generally can retry with success.
However, depending on the reason for the backup job interruption, additional issues can arise, one of these being topic of this post, which is change block tracking (CBT) no longer working.
This could be due to a number of reasons, such as a snapshot being removed during a backup, network or storage outage, to a host becoming inaccessible.
You will notice within the backup job's action log the following warning:
"CBT data is invalid, failing over to legacy incremental backup. No action is required, next job run should start using CBT again.
If CBT data remains invalid follow KB1113 to perform CBT reset. Usual cause is power loss."
Share this blog post on social media:
Tweet
Latest Blog Posts
- vSphere 7 U1 - Part 3 - Creating a Datacenter, HA/DRS Cluster and Adding a Host
- vSphere 7 U1 - Part 2 - Deploying vCenter 7.0 U1 VCSA
- vSphere 7 U1 - Part 1 - Installing ESXi 7.0 U1
- Veeam CBT Data is Invalid - Reset CBT Without Powering Off VM
- View Administrator Blank Error Dialog/Window After Upgrade
Popular
- Reset 3COM Switch to Factory Defaults (Forgot Password)
- Disk Consolidation Needed - Unable to access file since it is locked
- SCCM 2012 - Software Center Unable to Download Software 0x87D00607
- VMware Visio Stencils - Diagram and Icon Library
- Moving BT Infinity DSL from Master Socket to Any Household Extension Socket
- WSUS Useful Client Commands WUAUCLT.exe
- Creating/Adding a Raw Device Mapping (RDM) to a Virtual Machine
Social Links
Disclaimer
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.