https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMDc1IiwiaGFzaCI6IjM1OGQxMDRmLTU3ODgtNGU5MS1hYzNlLTI1YmE5MGMzYTJhNiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Backup and Replicas of virtual machines running on ESXi 6.0.x with Change Block Tracking (CBT) enabled may not be recoverable

Challenge

Leveraging VMware Changed Block Tracking (CBT) data supplied by VMware ESXi 6.0 can potentially render the data in backups or replicas inconsistent or corrupt.

Cause

This is a VMware ESXi issue in CBT logic that affects ESXi 6.0 through ESXi 6.0 Update 1a. It is resolved with VMware ESXi 6.0 patch ESXi600-201511001. Please see VMware KB article for additional information about the issue. 

Solution

Installing the patch alone is not sufficient, CBT reset is also required for all of your VMs. CBT reset is mandatory in every scenario, because existing CBT maps may already be inconsistent due to the original bug, which in turn may result in inconsistent full backups in future.

Please follow this article to reset CBT. Please note that performing Active Full backups cannot be considered as a substitute to CBT reset with this particular CBT bug.

More information

To download the patch, please go the VMware KB article KB2137545
KB ID:
2075
Product:
Veeam Backup & Replication
Version:
8.x
Published:
2015-11-17
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later