This morning around 6am, all running jobs in our (4.5) environment ended with a
50 status error.

Has anyone seen this happen before, any likely-cause candidates?  Where's a good
spot to start
troubleshooting this?

The '50' error is described as:

Status 50 description
----------------------------------
client process aborted
The client backup aborted. One instance when this code appears is if a
NetBackup master or media server is shut down or rebooted when a backup
or restore is in process.

As far as I can see, no-one manually shut down anything on our master.

Thanks for any help,
-Jay





This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.