Veeam.Archiver.Proxy RAM usage

[kevin3404]

Hey, all.

I am running both Veeam Backup and Replication and Veeam Backup for Microsoft Office 365 on a server. Recently, I noticed I was having issues with the Veeam B&R console not loading. I opened a support ticket #04785835 and support recommended adding RAM to the server. I installed an additional 32 GB of RAM into the server and the server is now using 48 GB of RAM.

The issues did improve for a few days, but came back after a short amount of time. I worked with support and we found that the Veeam.Archiver.Proxy is using massive amounts of RAM, sometimes going over 30+ GB of RAM.

This is absolutely having an inverse affect on the server and is causing the Veeam B&R console to slow down to a crawl when is is being viewed. Why is this consuming so much RAM? I did try editing the proxy's XML file for the proxy to add Params MaxCacheLimit = "8192" but this did not help, and it continues to consume massive amount of RAM.

I am running Veeam Backup for Microsoft Office 365 5.0.1.225.

[Mike Resseler]

VBO is using that much RAM when it is doing backup jobs. Most likely you are seeing this when 1 or more jobs are running. You say you have 48GB of RAM now, but depending on your size and jobs that might be not enough since I suspect that your VBO installation on the server is an all-in-one.

[Mildur]

In the Best Practice Guide, there is a table how many max objects you should backup with a 8 Core / 32GB machine. But this resources should be dedicated to VBO365.

https://bp.veeam.com/vbo/guide/design/maxconfig.html

[kevin3404]

VBO is using that much RAM when it is doing backup jobs. Most likely you are seeing this when 1 or more jobs are running. You say you have 48GB of RAM now, but depending on your size and jobs that might be not enough since I suspect that your VBO installation on the server is an all-in-one.

I did manage to limit the number of threads in use and it does seem to have helped with the amount of RAM being used and the jobs did not have a noticeable performance impact. I am going to continue to monitor this for the next few days to see how things are going.

[Mike Resseler]

Lowering the threads will get the RAM usage down, but it also means we can grab less data at the same time. However, that doesn't mean that your backup window will now increase. It all depends on many factors so it is a certainly a good thing to try