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: 66
Explanation: The client bpbkar process did not receive the message from the server that indicates that the server is ready to continue.
Recommended Action: Do the following, as appropriate:
Verify that the server did not crash.
On UNIX, Linux, and Windows clients, enable bpbkar debug logging.
Create a bpbkar debug log directory.
On a UNIX or Linux client, add the VERBOSE option to the
bp.conf
file. On a Windows client, set on the TroubleShooting tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client. Then select from the File menu.
On other PC clients, create a debug log directory for bpcd.
Increase the amount of information that appears in the logs.
See "Changing the logging level on Windows clients" in the NetBackup Logging Reference Guide.
Use the vxlogcfg command as described in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting debug logs.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.