VHDx:CVhdxLog.GetActiveSequence: VHDx disk was truncated

[mr2nut123]

Case ID: 00534162

Has anyone else had this with Veeam after shrinking a VHDx? Is there something else that needs to be done to prevent this error?

[foggy]

This error has not been reported here on forums previously, but according to QC there was a similar issue in some earlier versions that was addressed in version 6.5. What Veeam B&R version are you using? If it is v6.5 or newer, then please continue working with support regarding this issue. Thanks.

[mr2nut123]

This error has not been reported here on forums previously, but according to QC there was a similar issue in some earlier versions that was addressed in version 6.5. What Veeam B&R version are you using? If it is v6.5 or newer, then please continue working with support regarding this issue. Thanks.

It's the latest version with #3 installed. It was only after I shrunk a vhdx. They have provided me with a custom diag tool which I will run today as I was out of the office yesterday.

[KennethLarsen]

Just had the same error, on veeam 8. I extended the VHDX with just 1 gb, and ran an active full, and that worked !

[mr2nut123]

Good shout. I basically just had to reboot the Server for it to detect the changes. It must be the Software expecting a certain file size in the backup.

[PeterWR]

Just wanted to confirm this worked for me too!

Simply expanding a drive by 1GB - after it has been previously shrunk - allows the backup to proceed normally. I did not need to restart either host or VM for this truck to work.

Looks like Veeam does not understand a shrink, but can understand an expansion.

[FrankD]

Same problem, Version 8.0.0.2030

Disabled HyperV CBT - Not working
Run Active full - Not Working

Extended VHDX 1GB - Backup is Working Again.

[niconl]

I just had this same error with veeam 9.5. Extending the VHDX with 1GB is still doing the trick.