How to Thread multiple Server saves one after another.

[WhooTAZ]

I am still working with BE 11.d and trying to setup 3 or 4 threads with multiple servers per thread.  The idea is to have 3 - 4 threads that begin at a scheduled time and after the each server (with specific backup selection list) finishes saving the next server in the thread starts with it's own unique backup selection list.

Any help would be GREATLY appreciated.  I have worked with setting up the templates and the logic of "after 1 is done go to the next".  My problem is how do I get each server selection setup. 

Currently,  I have Backup Selection Lists for each server job and each job uses the selection list and is scheduled for a specific time.  This becomes hap hazard when more than 4 jobs are running if one takes much longer than in the past and mucks up the whole backup process.. Thus, I want to create "Threads" with multiple saves that begin one after another has finsihed.

Thanks Again!

[AmolB]

Why don't you create 1 job with all the servers selected in 1 selection list.

[Ken_Putnam]

You can either do as Amol suggests and just put everything into 3 or 4 jobs,

or you could use policies to execute your three or four "thread" with one job starting when the previous job in that thread ends

See the Admin Guide to set this up

[pkh]

Another way is to use BEMCMD as a post-command to start the subsequent jobs.  Read my blog below

https://www-secure.symantec.com/connect/blogs/use-bemcmd-start-jobs

[WhooTAZ]

I have figured how to link jobs with a policy but do not see any example or way to add another backup with a differect selection list.

I want to keep the saves seperate jobs to account for time and save size for each server.

[pkh]

You can only have one selection list per policy.