Proxy and Synthetic backups

[aich365]

Hi
We have a Veeam server backing up 60 objects and 122 disks.
A Veeam proxy is also installed.

it seems when a Synthetic Full is in progress then all jobs are queued to the Proxy Server.
Some of the Synthetics are taking 60 hours which is leading to long delays in processing other backups as they wait in queues.

If Synthetic Backups (merging) is running will the Veeam Server offload all jobs to the proxy regardless of the load on the proxy?
Thanks

[Shestakov]

Hi Clive!
Usually target repository is the bottleneck on synthetic full runs rather than proxy.
Could you provide the detailed bottleneck statistics?
Backup Server should not be loaded in any case.
Thanks!

[veremin]

Just a guess - but don't you leverage a CIFS share as a target repository by any chance (in this case backup server is selected as a default gateway server)?

[aich365]

Hi Thank you both for the response.

CIFS is not used.
The Repository is a NAS attached via iSCSi and presented in Disk Management as E: Drive and F: Drive.

The bottleneck shows as target.

I was more curious about why the 2nd proxy seems to be used exclusively for backups and when this proxy is busy jobs are queued but the Backup Server proxy is not used to share the Proxy load?
Thanks

[Shestakov]

Since the bottleneck is target, proxy load is not an issue.
General recommendation in this case is either to switch to less IO operations intensive backup mode or upgrade the target repository.
Could you provide full bottleneck statistics including source, proxy, network and target load?
Thanks!

[foggy]

I'd also check the maximum allowed number of concurrent tasks for the proxy and repository.