There has been a lot of discussion lately about a VMware Change Block Tracking (CBT) bug that causes backup software to miss out on modified parts of VMDK files. This results in corrupted backups.
The Register has had two articles about it:
The articles point to this VMware Knowledgebase link, and mentions that there is no fix available from VMware. Ouch!
Well of course since Actifio uses VMware Change Block Tracking (CBT) to capture images of VMs, my first thought was sh… ahh actually this is child friendly blog… but you get the idea. Were petabytes of client data at risk of being bad?
Fortunately the answer is a resounding no. Actifio does not depend on this particular API because we saw the potential for a flaw like this a long time ago. In fact we changed the way we use the VMware APIs in 2012 to ensure this API could not affect us
Actually we were that concerned about data integrity when using external APIs that we developed a feature we call Fingerprinting to ensure the integrity of our images. With every image that Actifio creates, Actifio uses a sampling technique to confirm that the image created in Actifio’s storage pools is the same as the source we were fetching data from. This applies to both VMs and to images created by our Connector software.
So with this Actifio customers can be assured that all available virtual images are free of any corrupt data due to CBT, backup calls, or any other capture procedures.