Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

ESXi is telling fibs to backup software

Embiggened VMs may not be backed up until you turn off CBT and turn it on again

Redditor “tottenham12712” has pieced together a scary scenario for VMware users: ESXi might be feeding dud data to backup software.

VMware knows it has a problem. Indeed, it has explained in this knowledge base article that when vAdmins expand a vmdk file past 128GB, and Change Block Tracking (CBT) is enabled, the QueryChangedDiskAreas("*") command returns an incorrect list of virtual machine disk sectors.

As tottenham explains, that's bad news because some backup software relies on that data to determine what to back up.

Tottenham12712 goes on to quote an email he's received from Veeam containing the following grim news:

“But the main point is that your backups and replicas for all VMs that had its virtual disk size expanded beyond 128 GB at some point may be unrecoverable.”

The good news is that there seems to be a simple fix: turning it off and turning it on again, with the “it” being Change Block Tracking.

VMware's working on a proper fix and Veeam is working on updates to its software to take the flaw into account. ®

Similar topics

Similar topics

Similar topics

TIP US OFF

Send us news


Other stories you might like