VMware Changed Block Tracking Errors - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

VMware Changed Block Tracking Errors - Connect IT Community | Kaseya

SUMMARY

Changed Block Tracking Errors

ISSUE

Purpose

To assist customers who get failed VMware Backups due to Changed Block Tracking (CBT) errors.

Description

Customer has successful VMware backups for one (or more) Virtual Machine(s) (VMs). Now, customer removes this VM(s) from the inventory and adds it back to the inventory to some other ESX Server i.e. NO vMotion is performed. All of this is done manually. After this, the customer starts seeing failed backups for the same VM(s). The error shown is that CBT is disabled.

Cause

This happens due to ‘manual’ interaction of the customer with the movement of the VM. Some attributes of the VM(s) are lost/misconfigured.

Resolution

For Recovery Series/UEB Appliances:

Click on the concerned ESX Server on the left pane.
Click on “Reload VMs” on the “Backup > 1-Time Backup” or “Backup > Schedule Backup” page.
After this, Backups of those VM(s) will start succeeding, since our database gets the updated data.

For Unitrends Free:

Click on Protect, select the ESX/vCenter server to which the VM/s belong, click Options on top and click Inventory Sync
After this, Backups of those VM(s) will start succeeding, since our database gets the updated data.

Third-Party Sources

N/A