Primary Bottleneck: Proxy on my VM backups

[JasonPGTF]

Hi, I just added quite a number of new VMs to be backed up. The jobs are running quite slow and I notice on the completed job it's showing below.

11/1/2019 6:31:22 AM :: Load: Source 38% > Proxy 89% > Network 75% > Target 16%
11/1/2019 6:31:22 AM :: Primary bottleneck: Proxy

How do I find more info on the Proxy bottleneck?
My current proxy is a 4 vCPU server with 4GB RAM. Should I increase the CPU or add another proxy server?

[Vitaliy S.]

Hi Jason,

What backup more are you using? I assume it is HotAdd, right? What's was the CPU usage of that proxy VM? Trying bumping up the CPU resources to see if the bottleneck shifts to network further or not.

Please keep in mind that there will always be a bottleneck (a thing to improve) regardless of how you set this up.

Thanks!

[foggy]

Is it a dedicated proxy or does it also run some other Veeam B&R roles (management server for .ex.)? Please keep tasks concurrency in mind as well, typically a single vCPU is required for each additional concurrent task.

[PetrM]

One more idea is to check compression level which is selected in backup job settings. High compression algorithms provoke higher CPU usage.
You may try to change it to Dedupe-friendly level or to disable at all.

Thanks!