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

VMware CBT Requirements

KB ID: 1163
Product: Veeam Backup & Replication
Published: 2011-08-19
Last Modified: 2021-07-26

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.
KB ID: 1163
Product: Veeam Backup & Replication
Published: 2011-08-19
Last Modified: 2021-07-26

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.