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.
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
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.