Hi,
the last days I discovered something in many forums and blog posts around the world which makes me really worried. It seems that with ESXi 6.0 and VADP (especially CBT) there might be a major and very disastrous bug. VMware covers it here VMware KB: Backing up a virtual machine with Change Block Tracking (CBT) enabled fails after upgradi...
Problem is, they are only talking about a CBT issue which produces some errors. They are *not* talking about potential data corruption. And I am talking about the running production VM from where the snapshot was taken.
Now - when looking at posts like this here: ESXi 6.0 CBT issue | view topic (there are many more on the net) I am wondering if somehow the snapshot commit operation in ESXi 6 is producing data corruption. Maybe it is only the VADP-triggered snapshot commit and (again) maybe there is more - some posts could even suggest that a partially snapshot rollback is accidentally triggered instead of a snapshot commit.
So - from my point of view - these problems are extremely serious and maybe disastrous. If VMware is aware of anything like this I would highly recommend to set a global letter to all customers, at the least to update the knowledge base article.
Is there any news around here in the forum?
Best regards,
Joerg
I am going to watch this thread. We have been working on restoring our Exchange server that was corrupted this morning from a replication from Veeam.
Trying to decide on rolling back to 5.5, or staying with 6.0 and wait for the patch.
Thanks,
Having the exact same issues! VMware support has been no good to me as of yet. Still waiting on a reply
Looks like VMware has finally fixed this CBT issue: VMware KB: VMware ESXi 6.0, Patch ESXi600-201505401-BG: Updates esx-base