Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 50
Explanation: One of the following has occurred:
The client backup terminates abnormally. For example, a NetBackup master or media server is shutdown or restarted when a backup or restore is in progress.
An administrator uses an OS-provided command line (for example, the kill command) to kill an active process. The job status does not reflect the change until one hour later, when the status changes to DONE and this status code is generated.
Recommended Action: Do the following, as appropriate:
Enable detailed debug logging.
Create a bpbkar debug log directory (UNIX, Linux, and Windows clients only).
Create a bpcd debug log directory.
On UNIX clients, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf
file.On PC clients, increase the debug or log level.
See "Changing the logging level on Windows clients" in the NetBackup Logging Reference Guide.
Retry the operation and examine the resulting logs.
This error may occur if nbjm terminated while a backup job was running. Examine the unified logging files on the NetBackup server for nbjm (117) for more detail on the error. All unified logging is written to
/usr/openv/logs
(UNIX) orinstall_path\NetBackup\logs
(Windows).On UNIX clients, check for core files in the
/
directory.On UNIX clients, check the system log (
/usr/adm/messages
on Solaris) for system problems.This problem can sometimes be due to a corrupt binary.
On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and tar binaries, which are located in
/usr/openv/netbackup/bin
on the client. Reinstall them if they are not the same as in the client directory under/usr/openv/netbackup/client
on the server.On a Windows client, check the
bpinetd.exe
,bpcd.exe
,bpbkar32.exe
, andtar32.exe
files, which are located in theinstall_path\NetBackup\bin
folder on the client.Reinstall the client if these files are as follows:
Not the same size as on other Windows clients
Not at the same release level
Do not have the same NetBackup patches as other Windows clients
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.