Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

How to kick off a job with a postscript

Created: 30 Jun 2011 • Updated: 23 Nov 2012 | 4 comments
This issue has been solved. See solution.

Hi all,

My issue is we run many of dozens of jobs a night, and we usually have a few jobs "fail" because they missed their window to start the backup, mostly because of other jobs running longer than they usually do.What I would like to do is have a postscript command to kick off the next job. So basically I can schedule one job manually, then have a postscript in that job kick off the next job, and so on.

Is that possible.

Comments 4 CommentsJump to latest comment

sazz.'s picture

Not heard of postscript just to run the job though you migh be able to do it using the BE command line. The best way to increase the time windows for your jobs or have a plan after monitoring your jobs. Once you have the jobs monitored you should have a fair idea as how long a particular job takes and you can then put the schedule as per your requirement.

Steve_Trinitas's picture

Thanks for your reply. The problem is that we are talking about many, many dozens of jobs, running on different tape libraries, backing up serveral remote campuses. So a job that usually takes 2 hours to run may all of a sudden take 3 or 4; the reasons vary from bandwidth issues to remote serer load issues, many of which are out of my control. So, yes I have already "monitored you should have a fair idea as how long a particular job takes and you can then put the schedule as per your requirement." But in this case it doesn't solve the issue.

Thanks agian for taking the time to respond.

Ken Putnam's picture

I assume that by "postscript" you are referring to a POST job?

This was the way we used to do it before policies were developed

Create the job

Create a CMD file to use BEMCMD to call the job (remember to include a path statement or absolute paths on all commands since there is no environent when the POST job runs

Stick the CMD file in the POST job command

If this response answers your concern, please mark it as a "solution"

pkh's picture

You can use BEMCMD to start your next job.  See my blog