CBT reset after Hyper-V patching

[collinp]

Once every 2 months, we patch all of our Hyper-v Win2k8r2 hosts in the cluster with Windows Updates and relevant Hotfixes. When we do this, it appears as though Veeam resets all CBT info and all of our Hyper-v VM jobs, with 70+ VM's, start anew and go back to doing full scans. As though we were running our very first full scan backup job. The first backup after such updates takes days until CBT kicks in after the next backup cycle.

Are there any plans in future releases to retain CBT info throughout Hyper-v host patching cycles? I understand that some MS hotfixes are correlated to clustering and CSV's, but shouldn't the Veeam CBT info being stored in a separate 'space' from the MS updates and be unaffected by the updates?

[Gostev]

The answer depends on what specifically causes CBT to reset in your case. Could you open a support case, and have our engineers investigate the logs from last occasion of this behavior. Please include the support case ID here for future reference. Thanks!