Well the Veeam KB article says there are two ways to reset the CBT. One is powering off the VM, that is a no go. The next is a VM CLI Powershell, which I can certainly do, but it states that it creates a snapshot then removes it which can stun the guest VM. This action DOES stun our vm's which is why we run backup windows and Veeam runs after hours (so when those snapshots are told to consolidate, no-one is here to experience anything, and our website is just slow or down for a minute or two).
So I agree if Veeam could do this to the VM right before it performs that VM's backup, great! Of course you wouldn't want this every time but scheduled would be ok. Perhaps monthly? Or perhaps after the restore points recycle (ie if you hold 14 restore points, backup #15 resets cbt then recycles oldest restore point and begins new backup).
But what should I do now? I'm not sure I have CBT bugs because I restored a few machines in the past, and My latest SureBackup lab seemed to work. Granted it was not the entire environment, just a very small percentage of backups, but shucks, I really want to upgrade and now this is in our way.
We are on ESXi 5.0.0 2312428