Ask the Community
Groups
Getting Changed Block Tracking (CBT) errors on Virtual Machines that have CBTenabled - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Getting Changed Block Tracking (CBT) errors on Virtual Machines that have CBTenabled</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>How to fix Changed Block Tracking (CBT) error.</p> <h3 data-id="description">Description</h3> <p>Fulls succeed but incremental or differential backups fail with an error that states that CBT is not enabled!</p> <h3 data-id="cause">Cause</h3> <p>Unitrends vProtect backup failed to enable CBT either due to existing snapshots or unsupported devices such as Raw Disk Mappings (RDM).</p> <h3 data-id="resolution">Resolution</h3> <p>*** The virtual machine owning the disks to be tracked must be hardware version 7 or later. ***</p> <p><br>1) Run a full backup for the vm client getting the error. Then go into schedules, select RELOAD and SAVE. Then run an incremental or differential backup. Doing a reload will update the database.</p> <p>2) Remove any existing snapshots.</p> <p>3) Ensure VM is not using RDM.<br><br>See <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%3D1020128">this</a> article for more information.</p> </article> </main>