Backup Exec 2010 - How to set a concurrent Backup Job on Post command

[JJCRUZ]

Hi to all,

I'm been working on the BExec server to set a job as a post command.

Problem Case:

We run several jobs for different types of backups. (SQL, Data, etc).  When we came the next morning the job for just one unexpected issue in one of the server the backup fails.

To resolve the problem we need to run the same job again that has like 15 servers attach to it.  If for some other error on other server the job fails again.

Question or Doub:

We like to create separate jobs for the servers and run them with the post command.  (Is that posible or there is another way to do it).

By that way if one job server fails we only need to run this particular job.

Is this souds logic or I'm a little confuse.

[pkh]

It is a good idea to break up the job.  Backing up 15 servers in one job is definitely too much, as you have experienced.  After you have broken up your job, there res 2 ways to solve your scheduling problem.

1) stagger the start time of each job.  For example, start each job say 10 minutes apart.  If they are all writing to the same resource or backing up from the same resource, the later jobs will queue until the earlier job finished.  Make sure that your time window is big enough for the job to wait.

2) if your jobs has dependencies, then put the later jobs on hold after specifying that they "run now".  In the post-command of your preceding jobs, put in something like

"C:\Program Files\Symantec\Backup Exec\bemcmd.exe" -o1 -j"<job name>"

and you can specify that they run if the preceding job is successful or not.

[Kiran_Bandi]

Unfortunately we don't have Checkpoint restart option with BE.

You can probably divide the job into three or four.

Scheduling will not be a big task if you have a library with more than one drive in it.

[Hywel_Mallett]

As well as staggering the start time of each job, you can also use job priorities to ensure that important jobs run first.

[Ken_Putnam]

As others have said, separate jobs is always a good idea

You can either use Policies to run jobs sequentially

or use BEMCMD to kick off a job when the current job ends