For a while, I was getting it every 10 minutes for every backup job.  This 
seemed to be a timing issue, caused by one of our media servers being down.  
When we brought it back up again, everything (almost) started working again.

We too see status 50's during duplicate operations (running the 4.5 Vault 
option), but haven't reported it to Veritas yet.

The immediate problem I'm trying to solve involves jobs that don't get 50's - 
they show active even though the BPSCHED process is gone on the master server.  
Rebooting the server will turn these jobs into 50's, but I prefer some way that 
doesn't include a server reboot.

I did try restarting the "NetBackup Request Manager" service today to solve a 
different problem: NetBackup stopped scheduling new jobs.  All active jobs 
continued without interruption - no error 50's.

-Michael


-----Original Message-----
From: Anderson, David [mailto:anderson.david AT scrippshealth DOT org]
Sent: Tuesday, September 24, 2002 4:40 PM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'; Niehaus, Michael T.
Subject: RE: Killing/deleting hung jobs with NBU 4.5


Sorry, I'm way behind in the list, but here you go...

I just latch on that you are having Status Code 50 errors.  I too am having
this particular error code during almost all Tape Duplications.  What I do
is manually reset the drive, then reboot the server.  Rebooting seems to be
the only way to get things working again.  I have an open case with Veritas
right now.  They acqnowledge that the error logs are capturing the codes,
but they can't duplicate it (so far).

Exactly WHEN do to get status 50's?

David Anderson
ScrippsHealth Information Services
(858) 678-6238
[Tieline: 318-6238]
anderson.david AT scrippshealth DOT org


--__--__--

Message: 2
Subject: RE: [Veritas-bu] RE: Killing/deleting hung jobs with NBU 4.5?
Date: Thu, 19 Sep 2002 17:01:40 -0500
From: "Niehaus, Michael T." <MTNiehaus AT MarathonOil DOT com>
To: <veritas-bu AT mailman.eng.auburn DOT edu>

I tried the command - it didn't work.  I tried deleting the files in
ffilelogs - that didn't work either.

Will shutting down the services result in current jobs ending with a status
50?  What are the other consequences?

-Michael