Ask the Community
Groups
Serious VMware vSphere 6 Changed Block Tracking Bug - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Describes a serious CBT bug in vSphere 6.0 environments.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="description">Description</h3> <p>Release 8.1 for Recovery-Series and Unitrends Backup appliances and software will support hypervisor-level backups for vSphere 6.<br>At the time of this KB, internal testing with vSphere 6.0 has exposed a bug in the changed block tracking (CBT) code of the hypervisor that can cause data corruption and unrecoverable backups. VMware has confirmed the issue, and has released <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D2114076">KB 2114076</a>.</p> <p><i><b>Note:</b> This can affect anyone doing hypervisor-level backups with vSphere 6.0</i>.</p> <p>We continue to work with VMware on the issue and will update once VMware has released a fix.<br>As a result, we recommend that you do NOT upgrade to vSphere 6.0 if you are doing hypervisor-level backups using VMware. If you are using vSphere 6.0, we recommend leveraging guest protection at the file- and application-level to ensure those VMs are protected efficiently until VMware provides a fix for the CBT issue.<br><br><u><b>UPDATE</b></u><br><br>VMware has issued a patch and they have acknowledged that the issue has been resolved. This is the pertaining KB - <br><br><a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D2116127">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2116127</a></p> </article> </main>