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.

Status Codes<br />

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

5. Verify that the robot number and host in the storage unit configuration matches what<br />

is specified in the Media Manager device configuration.<br />

6. Verify that the master server can communicate with the bpcd process on the server<br />

that has the storage unit.<br />

a. Verify that bpcd is listening on the port <strong>for</strong> connections.<br />

On a <strong>Windows</strong> <strong>NetBackup</strong> server, executing<br />

netstat -a<br />

prints out several lines of output. If bpcd is listening, one of those lines is similar<br />

to the following:<br />

TCP myhost:bpcd 0.0.0.0:0 LISTENING<br />

Do this on the server where the storage unit is connected.<br />

b. If bpcd seems to be operating correctly, create bpsched and bpcd debug log<br />

directories and retry the operation. Check the resulting debug logs <strong>for</strong> records of<br />

an earlier failure.<br />

After each backup, the scheduler checks the storage unit to see how many drives<br />

are available (in case the backup caused a drive to be automatically downed). If<br />

bpsched cannot communicate with bpcd, it sets the number of available drives<br />

in that storage unit to 0 and further backups to that storage unit during this<br />

backup session will fail.<br />

The number of available drives remains at 0 until the scheduler is initialized<br />

again.<br />

c. If the cause of the problem is not obvious, per<strong>for</strong>m some of the steps in<br />

“Resolving Network Communication Problems” on page 21.<br />

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

Message: database system error<br />

Explanation: The bpdbm process (<strong>NetBackup</strong> Database Manager service) could not create<br />

a directory path <strong>for</strong> its configuration catalogs due to the failure of a system call. This is<br />

usually due to a permission problem or an “out of space” condition.<br />

Recommended Action: Create a debug log directory <strong>for</strong> bpdbm and retry the operation.<br />

Check the resulting debug log <strong>for</strong> in<strong>for</strong>mation.<br />

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

Message: continue<br />

144 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<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!