This error happened after a power failure, where my hosts powered down without the guests being powered down first.
Veeam was basically unable to freeze the VM’s to take a hot backup. The backup would complete however, but be extremely slow in the process. This is a result of Changed Block Tracking not telling Veeam what blocks have changed in an incremental (or full) backup.
A lot of sites, including Veeam’s KB page, have suggested changing the CBT parameters in the offending VM’s, but this involves shutting down the guests.
What worked for me was much less invasive.
Edit the existing Veeam job, and click on Virtual Machines
Click the Recalculate button to the right. I initially saw the calculated size was indeed zero, so it had no idea of the machine sizes it was backing up
Once the machines/folders have recalculated and you have sizes populated, click Finish. This should then re-populate the Veeam database.
Hopefully you’ll have no more warnings, and also have a much faster backup timeframe.
Thanks for this. Your recalculation tip fixed the CBT: Soap Fault on 2 VMs in our network that rebooted due to a power cut. Didn’t need to shutdown the VMs so very happy about that. Thanks again.
Worked great! Awesome tip!
Hey, thanks! no need to reboot with this method. worked great.
worked like a charm, thanks mate
Thank you so for this! 🙂
Thanks for the tip.
Perfect. Thanks!
Thank you so much.It works perfect.
Works Perfect ! Thanks !
This tip has saved me so much time as I had dozens of VMs with this issue after an abrupt power incident. Thank you. How in the world did you figure this out? I always assumed the Recalculate button was just gathering sizes of VMs to help you estimate backup storage needs. Had no idea it would have an affect on CBT. Again, thanks for this tip.
Thank you very much. Worked for me as well!
Thanks for the great tip. It saved me much time and the reboot of 15VMs!
That also worked for me. Great, thanks for sharing this info 🙂