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: 49
Explanation: The client failed to start correctly.
Recommended Action: Do the following, as appropriate:
Make sure that software is installed on the client and it is the correct version. If necessary, reinstall the client software.
Check for full file systems on the client.
Enable detailed debug logging on the client by doing one of the following:
Create bpcd and bpbkar (UNIX, Linux, and Windows only) debug log directories.
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf
file.On Windows 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.
On UNIX or Linux systems, use the UNIX sum command to check for corrupt binaries.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.