VMware CBT Requirements

KB ID: 1163
Product: Veeam Backup & Replication
Published: 2011-08-19
Last Modified: 2021-07-26
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

This article details the requirements for Change Block Tracking (CBT).

Solution

CBT requirements include:

  • ESX(i) Hosts version 4 or later
  • VM being backed up must be at least hardware version 7
  • VM being backed up cannot be configured as a proxy within Veeam

 

You can find more information about Changed Block Tracking in the user guide.

More Information

Starting with Veeam Backup & Replication 7, VMware native CBT can be enabled when a VM has a snapshot present. However, in some rare situations, it may still be possible to get the warning "Changed block tracking cannot be enabled: one or more snapshots are present," in that case, you should remove all VMware Snapshots from the VM.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.