Create job where VM's do not get backed up concurrently

[KiwiJJ]

Hi,
Is it possible to create a single backup job where one VM won't get backed up until the previous one finished, for example I want to put the Exchange servers into a single job but don't want them running concurrently as I don't want them being snapped at the same time.

thanks,

John

[slos]

You could constrain the number of possible running tasks via the repository or proxy. Set of values low enough to accomplish this.

[KiwiJJ]

Hi Steven,
The problem with that is I have other jobs where I want them to run a lot of VM's at once as the proxy has a lot of resources. This is just for a job for Exchange Servers that are in a DAG and I don't want them failing over and another job for our domain controllers where I don't want them being snapped at the same time.

[Dima P.]

In such case you can use job chaining: create one backup job with regular schedule and second job scheduled to start after the first backup job.