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: 64
Explanation: The client did not send a ready message to the server within the allotted time.
Recommended Action: Do the following, as appropriate:
On all clients, enable bpcd debug logging as follows:
Create a bpcd debug log directory on the client.
On a UNIX or Linux client, 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.
On a UNIX, Linux, or Windows client, create the bpbkar debug log directory on the client.
On Windows clients, verify that the NetBackup Client service is running.
On a UNIX or Linux client, use the ps command to check for a client process that uses too much CPU time.
Retry the backup and examine the debug logs for clues on the cause of the failure.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.