VeeaMover memory usage

[spiritie]

Hi Forums / Veeam

We've been using the "Move" function quite a lot to move backups to S3.

Anyone else experienced that it uses A LOT of memory?

I don't know if it's related to a bug we've seen where the Move Backup will start out to respect the "max concurrent tasks", but as time goes all of the objects in a move session will be moved at the same time.
We have jobs where Veeam is trying to move 100-200 VM's at a time, this of course is not optimal from a performance standpoint.

We've seen 48 GB of memory on gateway servers disappear quite quick and ultimately crashes the entire OS because 0B memory is left.
(We have to use gateway servers, as the source jobs are on immutable repositories, and they cannot copy straight to S3)

[Gostev]

Hi, we would be happy to look at this if you could collect the logs and open a support case next time you experience a failure like that. As Move Backup not respecting max concurrent tasks value is certainly not an expected behavior. Thanks