Eject Media after job fails?

Christiaan Odendaal's picture
Christiaan Odendaal
November 4th, 2009
Eject Media after job fails?
 
I have recently noticed at some of our clients that after a job fails (particularly a media related failure) the tape gets ejected? How can I turn this off?
 
This feature makes it impossible for me to re run the job if it happens to fail.
Filed under: , , ,
0 votes
pkh's picture
pkh
2 weeks 3 days ago

Under the job properties,

Under the job properties, uncheck the Eject Media After Job Completes checkbox

_____________________

If this solves your problem, please mark this as the solution.

+1 (1 vote)
Christiaan Odendaal's picture
Christiaan Odendaal
1 week 6 days ago

Thanks, but that option

Thanks, but that option ejects the tape if the job completes. It is already disabled.
I am referring to when the job does not start. If the media is write protected and an alert is displayed, the media gets ejected.
0 votes
CraigV's picture
CraigV
1 week 6 days ago

Hi Christiaan, That happens

Hi Christiaan,

That happens when the tape isn't scratch. It's going to get ejected either way.
What I have done with this is to manually erase the tape before the job started.

If you find this is a solution, please mark it as such.

0 votes
pkh's picture
pkh
1 week 6 days ago

If the media is write

If the media is write protected and an alert is displayed, the media gets ejected

This action is so that you can insert an overwriteable media.  This is the logical action and is the way BE is designed.  If the tape is not ejected, you would have to eject it to insert an overwriteable media.  BE is trying to help the user.

If the media is write protected, re-running the job will  not help as it would still be write protected.

If the media is overwriteable and the job failed halfway, it would become write protected according to your overwrite protection period specification.  It cannot be re-used immediately.
 

0 votes
Christiaan Odendaal's picture
Christiaan Odendaal
1 week 6 days ago

It’s not only with

It’s not only with write protected.
 
This is causing major problems as we use Policy based jobs, with template rules.
We have 2 Policies which run daily. For weekends we have 2 jobs to run on the weekend. The same policy contains jobs for month end, both use different media sets. There is a template rule to supersede the weekend if it conflicts with the month end. The supersedes works and the job will go into queued until it times out and fails. After the month end firs Policy completes the superseded job will try and start, at this point an alert is generate and the media ejected. After a while my second policy starts and fails because there is no media.
 
This use to work perfectly and the media did not eject.
0 votes
CraigV's picture
CraigV
1 week 6 days ago

Any changes to your

Any changes to your environment like drivers updates, software updates etc.?

If you find this is a solution, please mark it as such.

0 votes