Implementing "rules" to run jobs one after the other??

[Kevin_Nickson]

I'm wondering if anyone knows how to setup multiple jobs to run one after the other? Basically, I want one job to finish before another starts. With 10d and NO Win2K3 SP1, I was able to run three or four jobs at once with no issues.

Now, with Win2K3 SP1, 11d maxes out my CPU and the server basically becomes useless. I've thoroughly tested this particular backup server and when running a backup even on one job, the CPU utilization climbs to 100% after about two hours. It was suggested by Symantec Customer Support that I only run one job at a time. Even though I don't think that will make a difference, I'm going to do it just to see. It's Friday so I have a bigger backup window to play with.

Thanks in advance for any assistance in setting this "rule".

[Philip_Pearson]

You could try a backup script to setup your job,

call the script using bemcmd.exe in a batch file.

Put multiple lines in the batch file each calling the next job.

The batch file should not move to the next line until the job called by the previous line has completed.

Never done it but worth a try.

[Hywel_Mallett]

You could do this using a policy, then using policy rules to start the second job after the first has finished.

[Philip_Pearson]

Sounds easier

[Ken_Putnam]

You can use BEMCMD, but rather than cmd file called by task scheduler

Use the POST job facility to call the next job in line using BEMCMD