Error in VBK Extract Utility

[WuttiW]

When we opens our 4tb vbk file ( with Vbk extract tool ), we get an "Please Wait" Message and the tool generates a "bad allocation" error message.

what can we do ?

Case ID : 01064905

[tsightler]

You could try importing the VBK into VBR (even the free version) and extracting the data that way. Or obviously continue working with support to find the resolution.

[bk@virtualtn.com]

Is there any limitation on the size of .VBK or number of the VMS on the .VBK to use the tools
Thanks

[veremin]

There should be none, but do you see an opposite behaviour?

[bk@virtualtn.com]

I think that when the .VBK file exceeds 6TB, the tool generates a "bad allocation" error message
I searched everywhere but I did not find the info about the limitation

[veremin]

Extract.exe uses 32-bit architecture and cannot work with files exceeding certain limit (several TB) therefore. Apologize for confusion caused.

There are plans to release 64-bit version down the road. However, we cannot provide any ETA for now.

Thanks.

[downiej]

Can you please build a 64 bit variant of Veeam.Backup.Extractor.exe and Extractor.exe to allow better memory management on bare metal extract of virtual machines from very large backup files.

There is a current limit on the size of VBK file (not sure what it is but 1Tb file fails) and when implementing a disaster recovery solution to restore from bare metal I would like the ability to restore from my backup file (initial base build of Veeam environment into which I can import my incremental backups for full restore).

Currently to get round this I am backing up the core VM's for Veeam to a separate (small) backup file to allow base recovery.

Thanks,

Jim.

[veremin]

This requirements has been tracked already. Chance are, one of the next product versions will come with 64-bit version of extract.exe utility. Thanks.