12-14-2018 05:58 AM
Hi.
I had to disable the replication for a while and now there is a quite huge backlog.
Is there a way to limit the replication jobs running in the same time?
I would like to run let's say max. 20 replication jobs at once.
12-14-2018 06:35 AM
I believe this is ultimately controlled by Disk Pool I/O maximum stream numbers but you can also use SLP Parameters to limit the size of each replication job and lower Job Priorities for duplications so replication catch-up doesn't swamp other jobs.
Andrew
12-14-2018 06:44 AM - edited 12-14-2018 06:46 AM
12-14-2018 06:46 AM
As far as I know, this parameter limits all the trafic to the storage, including backup jobs. This is something I don't want to achieve. I created a new storage unit, pointed the replications to this new storage unit, but seems it has no effect on the backlog sessions. So this is definitelly not a solution.
12-14-2018 07:36 AM
Unfortunately SLP targets are Disk Pools not Storage Units. Hence decreasing the size of each SLP job may enable more backup jobs to be processed, however by default backups are the lowest job priority (0) so won't get preferential treatment over duplications (50000) or imports (85000). You could try temporarily increasing backup job priorities.
Andrew