Quick Question - Concurrent Tasks

[ignitor]

In our environment we setup multiple smaller jobs which are currently 'chained' using a post job activity command. Obviously the big issue with chaining jobs like this is if you need to take a VM out or add someone specifically in the chain somewhere. My question is fairly simple can we remove these chained jobs and kick them all off at once? In our proxy settings it says max concurrent tasks which I set to '1', does this mean it will only process the backup jobs one at a time? If so due to resource limitations I don't really want all the jobs to process at once, just queue at once.

[foggy]

Drew, yes, you should not chain the jobs to achieve the required concurrency. Setting the concurrent tasks limit on proxies allows to schedule jobs to start in the required order (for example, 10:00, 10:01, 10:02, etc.) and before starting actual processing, each job will wait until those started earlier are finished.

[ignitor]

Drew, yes, you should not chain the jobs to achieve the required concurrency. Setting the concurrent tasks limit on proxies allows to schedule jobs to start in the required order (for example, 10:00, 10:01, 10:02, etc.) and before starting actual processing, each job will wait until those started earlier are finished.

Excellent! This is new to v6 right? We just upgraded.

[foggy]

This is new to v6 right?

Correct.

[dellock6]

To reassure Drew, we run every night all our 30 backup jobs with some hundreds of VMs all at once at 21.00, with concurrent jobs limits in place.
Never had a problem, and we always see jobs waiting in the queue for their turn. Go with it without any worry

[ignitor]

To reassure Drew, we run every night all our 30 backup jobs with some hundreds of VMs all at once at 21.00, with cuncurrent jobs limits in place.
Never had a problem, and we always see jobs waiting in the queue for their turn. Go with it without any worry

I appreciate the re-assurance.