Limiting number of backup/Replica jobs

[marius roma]

Imagine a Veeam B&R infrastructure with 3 proxyies at the source site and 3 proxyies at the targer site.
Each proxy is coningured to support up to 4 concurrent jobs.
A large number of Backup and Replica jobs are scheduled.
I some circumstances I see a large number of replica jobs running while backup jobs wait for resources availability.
I need to ensure that at given moment no more than a given number of replica jobs start, so that there are enough resources for backup jobs.
How can I limit the number of concurrent replica jobs to leave reources free of backup jobs?
Should I configure replica jobs to use only proxyies at the target site instead of automatic selection?
Is there any smarter way, to avoid changing each individual job?
Regards
Marius

[veremin]

I think the best option you have is to tie replication jobs to particular source proxy (s) that has a particular number of max parallel tasks configured. Thanks.

[marius roma]

Thank you for your answer.
Do you mean a proxy at the source site o at the target site?
Please consider that we run Standard edition so we can set only one proxy.
Regards
marius

[veremin]

Do you mean a proxy at the source site o at the target site?

Source proxy, as this is the component shared between backup and replication jobs.

Please consider that we run Standard edition so we can set only one proxy.

Not sure whether I follow you on that, since Standard edition should not have any limits regarding maximum number of existing proxies.

Thanks.

[marius roma]

I apologize for the misunderstanding.
When I configure replica jobs with Standard Edition and I select a backup as the source (not a live VM) I can only set one or more "Target proxy" and I can choose them among a list showing all the proxyies at both sites.
Should I select only proxyies at the target (replica) site?
Regards
marius

[foggy]

If we're talking about replication from backup, then it has lower priority than the original backup job and should be interrupted once the backup job starts. So no need to limit the number of replication jobs in this case at all.