Backup Exec fails to terminate job on time

We have a customer using Backup Exec SBS Suite v10.0 Rev 5520 (BE Service Pack 3).  There daily backup is to a DAT72 drive & they've just hit the limit of a single tape (compression is on so actual size is subjective).  The backup job is set to terminate in 12 hours of start up, which is 17:00.  This way they should have their notification e-mails the next morning regardless of the state of the backup.

Since hitting the limit of one tape, the backup job (which fills the first tape well within the 12 hour limit) will sit there all night waiting for the second tape (quite correctly).  The problem that is occurring is that the job is not getting terminated by the 12 hour limit.  The backup job waits until the next day's tape is in the drive (typically around mid day) and completes the actual backup process.  The job doesn't get terminated until the verification stage begins & only then does the job seem to realise it is way over the 12 hour limit & kills itself.

Is this normal behaviour and how can it be fixed (including if it is not normal)?
LVL 19
BarthaxAsked:
Who is Participating?
 
glenn_1984Connect With a Mentor Commented:
I understand what you said...BUT...if a second tape if required, and it seems that it is....

If the time out was working correctly you would ALWAYS hit the 12 hour limit as there is no one there to put in the 2nd tape.  Are you saying you want the job to end anyway?

I so, go to the Alert Tab.  Then on the left click on Configure Alert Categories.
Find Media Insert (I assume that is what the alert you are getting is).
Check Automatically Clear After ## hours or minutes, with Cancel.
This will Cancel the job, but have whatever you did get on to one tape.
0
 
glenn_1984Commented:
I would assume that BE does not count the time waiting for a tape change.

The alternative method might be to backup c: drive and program files that do not change regularly once a week, during working hours.

Backup up data and critical info nightly...without the programs...to get back to one tape if possible.

We actually use three backups...static files (bi-weekly)...file that change but not often (weekly)...data (daily)
The first two are done during working hours with Advanced File Lock.
0
 
BarthaxAuthor Commented:
The customer is looking into reducing what they backup.  This isn't the first time I've encountered the issue, but it is the first consistent BE install that exhibits the problem and it just happens to be the one where the customer demands the backup report first thing in the morning *regardless* of the state of the backup.

I expect BE does count the waiting time as it normally cancels the job if no tape exists to start the job.  Also the wording of the setting is "Cancel job if not completed within".
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
glenn_1984Commented:
0
 
BarthaxAuthor Commented:
Hi Glenn,

That is the setting I was referring to as being set to 12 hours: "Enable automatic job cancellation" is enabled and the "Cancel job if not completed within" setting is 12 hours. :(
0
 
glenn_1984Commented:
Did you apply fixes, patches and topical antibiotic to BE...as per the link in the reference site above?
0
 
BarthaxAuthor Commented:
I admit I didn't follow the link first time, sorry.  Unfortunately, the http://seer.support.veritas.com/docs/277429.htm link references updates/upgrades for v10.0 to get *to* build 5520 - the customer is already on v10.0 build 5520.  The BE's Veritas Updates link (Tools menu) shows no updates available. :(
0
 
glenn_1984Commented:
I am still looking for a solution...
In the meantime...

Let's say the time out WAS working properly.  That means the backup itself would not finish.
Is this what you want?  If not, give me the complete scenario you would like to see.
0
 
BarthaxAuthor Commented:
That is the scenario: no matter what state the job is in (including normal backing still in progress), when 12 hours is reached the job is terminated.  The backup starts at 19:00 and lasts for 12 hours - if the backup has taken this long, the customer considers it an error (it normally only takes 5 hours at the most).  The customer normally gets into the office at around 07:30 and checks their e-mail: they are very busy & unless an e-mail is sat there indicating a success/fail, they are likely to not notice & hence the problem may go unnoticed. :(
0
 
BarthaxAuthor Commented:
Superb!  Exactly what the customer is after: the highest priority configuration issue the customer desires is that the job is terminated by the 12 hour mark no matter what status the job has. :)
0
 
BarthaxAuthor Commented:
Can't get much better than spot on. :D
0
 
glenn_1984Commented:
Great, thanks.
0
All Courses

From novice to tech pro — start learning today.