Troubleshooting guide

Chapter 4, Status Codes and Messages 113
Status Codes
1. Create a bptm activity log directory on the server.
2. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. On a
Windows NT/2000 NetBackup server, set the Verbose logging level option on the
Universal Settings tab in the Master Server Properties dialog (see “Using the
Configure - NetBackup Window” on page 57).
3. Retry the operation and check the bptm activity log file for information on the drive,
robot, and tape that is causing the timeout.
4. On a Windows NT/2000 NetBackup server (master or media), check the Event Viewer
Application log for error messages that indicate why the tape mount did not
complete.
Status Code: 66
Message: client backup failed to receive the CONTINUE BACKUP message
Explanation: The client bpbkar process did not receive the message from the server that
indicates that the server is ready to continue.
Recommended Action: Verify that the server did not crash. If that is not the problem and
you need more information:
1. On UNIX and Windows NT/2000 clients, enable bpbkar activity logging.
a. Create a bpbkar activity log directory.
b. On a UNIX client, add the VERBOSE option to the bp.conf file. On a Windows
NT/2000 client, set Verbose on the TroubleShooting tab in the NetBackup
Configuration dialog box. To display this dialog box, start the Backup, Archive,
and Restore interface on the client and click Configure on the Actions menu.
2. On other PC clients except Macintosh, create an activity log directory for bpcd (the
bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the logging topics
in Chapter 3.
3. On the master server create bpsched and bpbrm activity log directories. If there are
media servers involved, create a bpbrm activity log directory on them.
4. Retry the operation and check the resulting activity logs.