1-800-691-1991 | 9am - 8pm ET
EN

Changed block tracking cannot be enabled: one or more snapshots are present

KB ID: 3169
Product: Veeam Backup & Replication
Version: 10
Published: 2020-05-06
Last Modified: 2021-08-17

Challenge

After upgrade to Veeam Backup & Replication 10, the Backup of a VM using Cisco HyperFlex Snapshots completes with the warning "Changed block tracking cannot be enabled: one or more snapshots are present" if a Sentinel snapshot is already present.
The described issue with Cisco HyperFlex Snapshots was resolved in Veeam Backup & Replication v11.

Cause

Veeam Backup & Replication does not enable CTK during backup from Cisco HX for vSphere 6.5 and later hosts; as in this case, VMware may return incorrect CBT data.

Solution

Purpose and applicability of article
This article's solution applies only to environments where Cisco Hyperflex integration is in use. If this warning occurs in an environment not using Cisco Hyperflex, it indicates that a snapshot is present on the VM for which the warning occurs. The presence of that snapshot is preventing Veeam Backup & Replication from enabling vSphere native Change Tracking.  In such a situation, Veeam Backup & Replication cannot leverage VMware vSphere CBT but fails over to Veeam’s proprietary filtering mechanism.

As a workaround, please add the following registry key on the server where the Veeam Backup & Replication is installed:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: VMware65CbtSnapshotCheckEnabled
Value Type: DWORD (32-bit) Value
Value Data: 0

Note: Though the registry value name states VMware 6.5, it is effective on all newer versions of VMware.

KB ID: 3169
Product: Veeam Backup & Replication
Version: 10
Published: 2020-05-06
Last Modified: 2021-08-17

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.