bad allocation during disk upload in Veeam Backup for Google Cloud?

Hi,

Support case has been locked.

Veeam Support - Case # 07888865 - xyz  - bad allocation

To better understand what’s causing the bad allocation error, could you let me know exactly what type of restore you’re running, Instant Recovery, full VM restore, disk restore, or FLR? It would also help to know if the repository you’re restoring from is on the same Veeam server or if it’s on another server or storage location, because limited resources or slow I/O on the repo or mount server can lead to this kind of issue.

If you can, please share the part of the logs around the error. Those lines usually make it clearer whether we’re dealing with something related to memory usage, storage performance, or communication between data movers.

This type of error often comes down to repository health or a resource bottleneck. It might be worth checking the repo storage, trying a different mount server, or even testing another restore method just to see if the behavior changes.

Once you send the restore type, repo location, and the log snippet, we can narrow down the cause much more accurately.

This error could be many things and I suggest you stay with support on this one.  Too hard to give a definitive place to look other than logs.

as of now support is working on this issue.

as of now, Veeam support for the VAW team is looking into this matter, and logs have already been sent to support.

Bad allocation is 99.9% of the time lack of memory (RAM) on one of the backup components (proxy, repository, backup server itself, etc)

Continue with Support, but likely over time the job failed as memory got exhausted. You might check Windows Event log if your backup infrastructure is Windows based and look for memory exhaustion errors.