Backing up VMs in vSphere 6 can cause data loss in your backups! Earlier I wrote about critical bug with vSphere 5.5 update 3 related to backups which was absolutely unacceptable and here we go again…<\/p>\n
Here’s symptoms from VMware’s KB:<\/p>\n
When running virtual machine backups which utilize Changed Block Tracking (CBT) in ESXi 6.0, you experience these symptoms:
\nThe CBT API call QueryDiskChangedAreas() API call can sometimes return incorrect changed sectors, which results in inconsistent incremental virtual machine backups.
\nInconsistent virtual machine backups<\/p><\/blockquote>\nOf course, no fix yet but let’s take a look at the joke of a workarounds they suggest:
\n– downgrade ESXi to version 5.5 and change VM hardware version to 10
\n– Shutdown VM before doing incremental backup
\n– Do full backup daily instead of incremental
\nReally? Do you think any of these solution are applicable in production environment? Ha ha…<\/p>\nVMware’s KB 2136854<\/a>
\nI honestly feel horrible for IT Professionals caught by poor QA from VMware, yet again.<\/p>\nUpdate: 11\/26\/2015: VMware released patch to fix it: ESXi600-201511001<\/p>\n","protected":false},"excerpt":{"rendered":"
Backing up VMs in vSphere 6 can cause data loss in your backups! Earlier I wrote about critical bug with vSphere 5.5 update 3 related to backups which was absolutely unacceptable and here we go again… Here’s symptoms from VMware’s … Continue reading