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

Veeam B&R limitations for VHDX Live resize usage

KB ID: 2450
Published: 2018-02-26
Last Modified: 2020-08-13

Challenge

Live resizing of VHDX files (available in Windows 2012 R2 Hyper-V) will be causing following scenarios:

a)  If you shrink the VM disk the backup task for this VM will fail and the following exception can be found in the Agent.<Job name>.Source.<VM name> log file:
 
[date time] <  6440> cli| VHDX.GetDiskInformation
[date time] <  6440> cli|   (EString) DiskPath = vhdx://<shadowSpec><extent path="full path to the disk" shadow="full path to the disk in the shadow copy" isAutoRecovery="False" /></shadowSpec>
[date time] <  6440> cli|   (EString) Option.Container = {disk}
[date time] <  6440> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[date time] <  6440> vhd| Opening VHDX by full path: [full path to the disk].
[date time] <  6440> cli| File 'HostFile{full path to the disk in the shadow copy}' opened (read_only: true, no_cache: false)
[date time] <  6440> dsk| Loading VHDX log.
[date time] <  6440> dsk| Loading VHDX log. Failed.
[date time] <  6440> cli| File 'HostFile{full path to the disk in the shadow copy}' closed
[date time] <  6440> cli| ERR |Failed to process method {VHDX.GetDiskInformation}
[date time] <  6440> cli| >>  |VHDX file was truncated. Current file size: [1503242747904]. Flushed file size: [1825365295104].
[date time] <  6440> cli| >>  |Failed to replay VHDX log.
[date time] <  6440> cli| >>  |--tr:Failed to load VHDX log.
[date time] <  6440> cli| >>  |An exception was thrown from thread [6440].
[date time] <  6440> cli| Trying to poll message from the notification channel (from server side).
[date time] <  6440> net| Triggering AUX channel synchronization. Request id: {guid}
[date time] < 10260> net| Received synchronization response {guid}
[date time] <  6440> cli| No server exception available.
[date time] <  6440> cli| ERR |Failed to process {Invoke} command
[date time] <  6440> cli| >>  |Details:
[date time] <  6440> cli| >>  |VHDX file was truncated. Current file size: [1503242747904]. Flushed file size: [1825365295104].
[date time] <  6440> cli| >>  |Failed to replay VHDX log.
[date time] <  6440> cli| >>  |--tr:Failed to load VHDX log.
[date time] <  6440> cli| >>  |Agent failed to process method {VHDX.GetDiskInformation}.

b) If you expand the VM disk the backup of such a VM may become inconsistent.
 

Cause

Live resize of VHDX does not get metadata automatically flushed.

Solution

After performing Shrink of a running virtual machine you should shutdown the VM (not Reboot) and power it on again to make the backup job run successfully. However if you performed Expand of a running virtual machine and backup job for it has already run after expanding, you additionally need to start Active Full for it.
 
KB ID: 2450
Published: 2018-02-26
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.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

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 try again later.