VMware

Latest CBT bug

No one said too much on this thread that I saw. [https://www.reddit.com/r/vmware/comments/cvpi43/cbt_bug_on_revert_snapshot/](https://www.reddit.com/r/vmware/comments/cvpi43/cbt_bug_on_revert_snapshot/)

Veeam discovered a CBT bug. Could anyone confirm if it is global or just certain editions of Vmware? I have 6.5 for example and wonder if I am affected.

​

I would have assumed that making and reverting to snapshots is an extremely common practice at most companies and according to this and the official KB article by Vmware seen here [https://kb.vmware.com/s/article/71155](https://kb.vmware.com/s/article/71155) you are to expect that CBT can/will break if you revert.

​

so I mean most backup vendors use CBT I believe and everyone could right now have random broken backup chains…

Veeam says they recommend to stop using vmware snapshots altogether as they impact performance and fill up datastores, and now this….

So I am looking at trying to change our policy to use a quick backup instead of taking any snapshots anymore….

​

What do you all think?



View Reddit by adjacentkeyturkeyView Source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

One Comment

  1. /u/Gostev shared this update:

    > On to the next vSphere topic: invalid QueryChangedDiskAreas API output after reverting VM to a snapshot. Finally, I have a solid update to share: VMware has finished investigating the issue and confirmed current API behavior to be incorrect and NOT “by design”. So they’re now intended to create patches **for all supported ESXi versions** to address the issue. Presumably, they want to solve this by disabling CBT completely following VM snapshot revert operation. As you remember, this is exactly what I hoped they’d implement – and this certainly works for us: Veeam should be compatible with this change right out of the box. Because seeing CBT disabled on a processed VM, jobs will just re-enable it automatically (although of course, CBT data will be available for use starting the following job run only). Timelines for those patches are not however known yet.

    (Emphasis mine).

    Based on that, while there are no versions given anywhere I can find, based on the intention of VMware that they will patch “all supported ESXi versions”, you should asume that 6.5 is affected by this, as is 6.0 and 6.7 and quite likely 5.5 is affected as well (but will not be patched).

Leave a Reply