Video Screencast Help

The job was automatically canceled because it exceeded the job's maximum configured run time

Created: 01 Feb 2013 • Updated: 04 Feb 2013

We are experiencing this problem in BE 2102.  The job is automatically canceled because it exceeded the job's maximum configured run time.  The job was working fine for several weeks.  But now it gets this error and cancels but ONLY on Thursday night.  Here's a synopsis:

We upgraded to BE 2012 in late November 2012.  We currently have 4 backup jobs each running to a different server and runnning each night Sunday through Thursday. 

Job 1 starts at 6 pm and takes approximately 2.75 hours

Job 2 starts at 6:30 and finishes around 11 pm - since it has to wait for job 1 to finish.

Job 3 (the failing job) was sheduled for 7 pm but, of course doesn't start until after job 2 finishes. It generall takes between 2 and 3 hours to complete.

Job 4 (fails also) was scheduled for 7:30 pm and starts when job 3 completes. It generally takes around 6 hours to complete.

We originally had these running Monday through Friday but realized that if the backup went to 2 tapes no one would be here to insert a second tape on Saturday and the job would time out (after 20 hours).  Since we changed the jobs to SMTWTh, job 3 fails ONLY on Thursday night each week with the above error. ANd Job 4 fails behind it.

We deleted the jobs and recreated them. No change. 

Today I changed the start time on job 3 to 12:01 am and job 4 to 12:30 am.  I won't know if this will fix the problem until next Thursday.  But I am of a mind that we shouldn't have to do this.  And since the total will take 9+ hours, we will have a backup job running during working hours every day.

Does anyone know why this might be failing?  Where I might look to figure it out?  (I've looked at the BE logs and the event logs on both servers.)

Thanks in advance!