Changed block tracking cannot be enabled: virtual hardware version 7 or later required

KB ID: 1186
Product: Veeam Backup & Replication
Version: 4.x, 5.x
Published: 2011-08-25
Last Modified: 2020-08-13
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

The backup or replication job is processed slower than expected and gives the warning message “changed block tracking cannot be enabled: virtual hardware version 7 or later required."

The job works without Changed Block Tracking, and the “changed block tracking cannot be enabled: virtual hardware version 7 or later required” error can be seen in the job log.

Cause

The VM that is being backed up/replicated has virtual hardware version 4, which does not support changed block tracking.

Solution

You need to updarde the hardware version. To do so:

  1. Start the vSphere Client or vSphere Web Client and log in to the vCenter Server

  2. Power off the virtual machine

  3. Right-click the virtual machine and select the menu option to upgrade virtual hardware

    • In vSphere Client, the option is Upgrade Virtual Hardware

    • In vSphere Web Client, the option is Configuration > Upgrade Virtual Hardware

      The software upgrades the virtual hardware to the latest supported version.

      Note: The Upgrade Virtual Hardware option appears if the virtual hardware on the virtual machine is not the latest supported version.

  4. Click Yes to continue with the virtual hardware upgrade

  5. Power on the virtual machine

    Note: If the virtual machine has a Microsoft Windows guest operating system, the operating system detects a new device, configures the device, and prompts you to reboot the guest operating system. If any unknown devices are recognized, the operating system prompts you to configure the device manually.

  6. For Windows guest operating systems, reboot the guest operating system to make the changes take effect.

Click here to send feedback regarding this KB, or suggest content for a new KB.
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.