Updated Post – vSphere ESXi6.0 CBT (VADP) bug that affects incremental backups / snapshots.

VMware recently posted a new KB article 2136854 to advertise the issue. Which is great that this has finally been accepted and advertised to customers and partners. It’s important to know this is not the same one as posted recently also for ESXi 6.0 (KB 2114076) – now fixed in a re-issued build of ESXi 6.0 (Build 2715440) But it is very similar to KB 2090639 from a historical perspective. The Issue If you are leveraging a product that uses VMware’s VADP for backup, then chances are you are leveraging this for not just initial fulls, but regular incremental snapshots (for backup purposes). There are numerous products on the market that leverage this API, it’s virtually the industry standard to use this feature as it results in faster backups. When the incremental changes are being requested through the API (QueryDiskChangedAreas) the API is requested changed blocks, but unfortunately some of the changed blocks aren’t…

VMware Hardware Version upgrades – The manual way.

The below process is somewhat manual in the process, but it’s been validated a few hundred times by myself personally. I like to think of VMware’s Virtual Hardware as a virtual motherboard, I remember this explanation was included in the VMware JumpStart materials I used to deliver back in the VI 3.x days. And the Virtual Hardware comes with certain capabilities and restrictions. Newer motherboards are capable of more processors, more memory, more efficient, etc. And commonly, what you normally need to add/remove or replace on a motherboard is the same as Virtual Hardware, in that it often requires a power down to replace or upgrade such items. Yes Hot-Add has changed this somewhat, and definitely for the better, but it’s sometimes an afterthought in many peoples VM templates.