15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Chapter 4, <strong>NetBackup</strong> Status Codes and Messages 93<br />

Status Codes<br />

<strong>NetBackup</strong> Status Code: 65<br />

Message: client timed out waiting <strong>for</strong> the continue message from the media manager.<br />

Explanation: The tape manager, bptm reported that the media did not load and position<br />

within the allotted time.<br />

Recommended Action: Verify that the requested volume is available and the required<br />

device is in an UP state.<br />

For detailed debug in<strong>for</strong>mation:<br />

1. Create a bptm debug log directory on the server.<br />

2. On a <strong>Windows</strong> <strong>NetBackup</strong> server, set the Verbose logging level option on the<br />

Universal Settings tab in the Master Server Properties dialog (see “Using the Host<br />

Properties Window” on page 40).<br />

3. Retry the operation and check the bptm debug log file <strong>for</strong> in<strong>for</strong>mation on the drive,<br />

robot, and tape that is causing the timeout.<br />

4. On a <strong>Windows</strong> <strong>NetBackup</strong> server (master or media), check the Event Viewer<br />

Application log <strong>for</strong> error messages that indicate why the tape mount did not<br />

complete.<br />

<strong>NetBackup</strong> Status Code: 66<br />

Message: client backup failed to receive the CONTINUE BACKUP message<br />

Explanation: The client bpbkar process did not receive the message from the server that<br />

indicates that the server is ready to continue.<br />

Recommended Action: Verify that the server did not crash. If that is not the problem and<br />

you need more in<strong>for</strong>mation:<br />

1. On <strong>Windows</strong> clients, enable bpbkar debug logging.<br />

a. Create a bpbkar debug log directory.<br />

b. On a <strong>Windows</strong> client, set Verbose on the TroubleShooting tab in the <strong>NetBackup</strong><br />

Configuration dialog box. To display this dialog box, start the Backup, Archive,<br />

and Restore interface on the client and click Configure on the Actions menu.<br />

2. On other PC clients except Macintosh, create a debug log directory <strong>for</strong> bpcd (the<br />

bpcd log is created automatically on Macintosh).<br />

To increase the amount of in<strong>for</strong>mation that appears in the logs, see the logging topics<br />

in Chapter 3.<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!