priority between copy jobs?

[srdegeus]

In our environment we have a big VM (and a few smaller ones) and a few medium sized physical systems. All backup to a local repository and a Backup Copy job to Cloud Connect.

The VM is that big that we have a weekly schedule for the Backup Copy job, as it takes several days to copy. At the same time we have a daily Backup Copy job for the agent.

The issue I am facing is that both Backup Copy jobs share the bandwidth, due to this the daily job (sometimes) runs for longer than 24 hours and misses the copy interval.
Is there a way to give the Agent Backup Copy job a higher priority, so that this can finish (first)? (Without using the schedule on the VM copy as could cause the copy job still to be on 'pause' while the other job has already finished.)

[foggy]

If you had different repositories for VMs and physical systems, you could throttle network traffic between the one that stores VM backups and the target one, at the time the agent job is running.

[srdegeus]

They are on the same repository, but even if they were on different ones, wouldn't the throttling be more or less the same as setting the schedule on the Backup Copy job for the VMs? It has the same drawback that the traffic could still be throttled while the Copy Job for agents has finished. (With the exception that bandwidth would be limited to a value instead of 0.)

But you comment hints towards that it is not possible to set a priority? The two jobs will always share the bandwidth around 50/50?

[foggy]

Correct, it turns out to be a similar solution, yet a bit more elegant. Currently there's no other way to set priorities in terms of bandwidth usage.