Queuing jobs outside window EXIT STATUS 196 - Veritas Net Backup
This is a discussion on Queuing jobs outside window EXIT STATUS 196 - Veritas Net Backup ; Why does the scheduler queue up jobs when it "should" know
that they are already outside the backup window? Only then to have
them fail. It also appears that this is causing my drive to
go off line about every ...
-
Queuing jobs outside window EXIT STATUS 196
Why does the scheduler queue up jobs when it "should" know
that they are already outside the backup window? Only then to have
them fail. It also appears that this is causing my drive to
go off line about every five minutes or so which I find very
anoying, I am having to set here and constantly monitor the
device management window and watch when the drive goes off line
and then put it back on line manually. This is really a pain.
Is there some work around or some patch that can keep this drive
from going off line every five minutes?
-
Re: Queuing jobs outside window EXIT STATUS 196
Marc Summers wrote:
> Why does the scheduler queue up jobs when it "should" know
> that they are already outside the backup window? Only then to have
> them fail. It also appears that this is causing my drive to
> go off line about every five minutes or so which I find very
> anoying, I am having to set here and constantly monitor the
> device management window and watch when the drive goes off line
> and then put it back on line manually. This is really a pain.
> Is there some work around or some patch that can keep this drive
> from going off line every five minutes?
The sheduler should not queue a job after the backup window. I'd advise
creating a bpsched log to verify this, also, if you set VERBOSE in the
vm.conf and monitor you syslog ( is ./var/adm/messages, etc) you will
the the drive and robotic operations, and in there you will see it
explicity tell you why the drives are going down. then fix the problem.