Contained in the latest patch releases for ESXi 6.0 (November) and 6.7 (last week) is a fix for the an an issue that surfaced a few months ago in relation to a very specific condition upon reverting a SnapShot where CBT data might become corrupted.
Update: The patch for ESXi 6.5 was released on the 19th of December and can be found here
The VMwareKB has the information here.
- When reverting a virtual machine that has CBT enabled to a snapshot which is not a memory snapshot, you might see InvalidArgument error if you use the QueryChangedDiskAreas() API call. After you revert a virtual machine to a snapshot, change block tracking (CBT) data might be corrupted. When reverting a virtual machine that has CBT enabled to a snapshot which is not a memory snapshot, and if you use the QueryChangedDiskAreas() API call, you might see an InvalidArgument error. This issue is resolved in this release. With ESXi670-201912001, the output of the QuerychangedDiskAreas () call changes to FileFault and adds the message Change tracking is not active on the disk <disk_path> to provide more details on the issue.
In regards to Veeam customers, our SVP of Product, Anton Gostev highlighted the patches in his Weekly Forum Digest (which everyone should be following) and there has been an update to confirm all is well it comes to Veeam Backup & Replication working transparently with the fix from VMware.
The patch for 6.7 contains a number of additional fixes.. a lot of them centered around storage so it’s worth looking through the Resolved Issues section of the