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

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


 
KB ID: 1961
Product: Veeam Backup & Replication
Version: 8.0.0.817
Published: 2014-11-20
Last Modified: 2020-08-13

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.