VMware acknowledged a known issue (KB2136854) within ESXi 6.0 and 6.0 U1. CBT looses the information of I/Os during snapshot consolidation. The main backup isn’t affected but all data written during the consolidation task are missed.
ALL CBT incremental backups are potentially affected.
VMware currently has no resolution.
VMware released a patch for the CBT bug.
VMware ESXi 6.0, Patch ESXi600-201511401-BG: Updates esx-base (2137546)
Before you upgrade your ESXi 5.5 Server to the new version of ESXi 6.0, you have to check the support status of your hardware and the requirements of firmware and driver versions.
To apply updates to a standalone host you have to do some steps with putty and the esx command line, because vCenter Server and Update Manger are missing in this case.
It is also possible to do a complete upgrade within putty and esx command line.
In my last training Fabian Lenz and I discuss pro and con of power management in ESXi.
We thought DPM is mostly used in VDI-environments. In those environments the savings would be the best, because the virtual desktops didn’t work at night and many of the ESXi hosts could be powered off. But DPM ist not the only thing which affects the power consumption. ESXi could use ACPI C- and P-States from the CPU to control the power of the physical cores. Fabian experiements with a bigger VDI environment and gets interessting informations with activated DPM (watch his blog).
In vSphere 5.5 and 6.0 a new command was given to esxcli. With this command you can reclaim deleted blocks on thin-provisoned LUNs.
You could run the mechanism in production time. This might sound good…. Our maintainance windows gets smaller and smaller with every new service and if you could do maintainance when everybody could work is that great.
BUT one moment!
The ESXi host which runs the reclaim would get very high cpu usage and might costops VMs within the host. Especially the first run will take a lot of time.