Together with the latest version of the VCSA 6.7, it is also available the improved version of VMware ESXi 6.7 update3b. This build is pretty much a security and bugfix from the previous release. As a highly desired update, this one resolves the issue related to the CBT behaviour. When reverting virtual machines back to snapshots it could cause a Full backup due to corrupted CBT information.
As per VMware change log the info about the CBT issue is outlined as follows:
PR 2423301: 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
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.
With the fix, you must power on or reconfigure the virtual machine to enable CBT after reverting it to a snapshot and then take a snapshot to make a full backup.
To reconfigure the virtual machine, you must complete the following steps:
- In the Managed Object Browser graphical interface, run
ReconfigVM_Taskby using an url such as
https://<vc or host ip>/mob/?moid=<the virtual machine Managed Object ID>&method=reconfigure.
- In the
- Click Invoke Method.
The list of fixes is quite impressive and to have an idea the best is to check the official release notes from the VMware site.
VMware ESXi 6.7 update3b upgrade
In this article the steps on how to run VMware ESxi 6.7 update3b using VMware Update Manager (VUM). The process is pretty simple. It consists in creating a baseline and apply this one to the intended vSphere Hosts. From here the ability to check compliance and remediate (read apply patches).
First step from the vSphere Client > Update Manager > Updates it is a good idea to download the latest definitions for the intended baselines.
If the compliance check has not run or not scheduled it is a good idea to manually run it and verify the status.
At this point it is easy to identify which Hosts are not compliant.
Next step is to associate a specific baseline to a vSphere Host. As a personal preference, it could be useful to create custom baselines and divide them into quarters. Patches are in general always cumulative so no need to check for previous ones all the time. Plus in case of rebuilding a Host it will automatically download and apply the latest ones. Or specific ones in case of compatibility. Once ready hit on remediate.
In the next screen the options to customise the install behaviour including Host reboot. Very useful especially for Clusters with DRS functions.
VUM will upload the patches as per baseline definitions to the vSphere Host and run the VMware ESXi 6.7 update. A quick view on the Summary tab will reveal the build version.