Discussions specific to the VMware vSphere hypervisor
Post Reply
Posts: 38
Liked: 2 times
Joined: Nov 12, 2018 7:07 pm
Full Name: Vijay Kumar Gouni


Post by vijayG »

Last night Our data center has Power outage.
After Power restore, All servers are back to online along with Backup server.
I have initiated the Backup job for our servers. But each server incremental backup is taking more than 12 Hours. earlier it was less than 20-30 mins.
I found one message in the job history.

"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."

It is impacting the production. Please suggest how we can reset the CBT with out impacting VM/production.

Vijay G

Veeam Software
Posts: 563
Liked: 75 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic

Re: 04307704

Post by PetrM »

Hi Vijay,

Please find more information about CBT reset in this KB. However, it makes sense to reset CBT only if you notice the warning during each job run.


Andreas Neufert
VP, Product Management
Posts: 4368
Liked: 816 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany

Re: 04307704

Post by Andreas Neufert »

It is a typical VMware situation. ESXi Powerloss will leave the CBT file in a corrup state and as we can not use it, we will start in "Snap and Scan" backup where we 100% read the data and will detect changes (backup size is the same, but it will take longer as reported).

To fix this you can work with VMware support or reset the CBT as described above. Then the first run will again process Snap and Scan backup and proceed afterwards with normal incremental forever processing.

Post Reply

Who is online

Users browsing this forum: somoa and 33 guests