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

CBT does not track changes correctly on VHDX disks files larger than 2 TB

KB ID: 1961
Product: Veeam Backup & Replication
Version: 8.0.0.817
Published: 2014-11-20
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 Policy.

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

Veeam Change Block Tracking (CBT) driver incorrectly parses virtual disk file change information causing jobs to failover to “full scan” incremental passes (in case of VSS backup) or to create an empty incremental backup (in case of crash-consistent backup) when both of the following conditions are met:
  1. VHDX file size of a virtual disk is above 2 TB (actual virtual disk capacity is irrelevant).
  2. Hyper-V host version is 2012 or 2012 R2.

Cause

Bug in Veeam CBT logic.

Solution

Install the following Critical update rollup for Veeam Backup and Replication 8.0.0.817 to address this issue.
 

More information


 
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 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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.