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 5, Media Manager Status Codes and Messages 217<br />

Status Codes<br />

Explanation: A requested operation encountered a case where a volume query did not<br />

return a volume entry matching the search criteria.<br />

Recommended Action:<br />

1. Examine the daemon and reqlib debug logs <strong>for</strong> a more detailed message on the error,<br />

as follows.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the volume daemon/<strong>NetBackup</strong><br />

Volume Manager service, or start vmd with the verbose option, if available.<br />

b. Retry the operation and examine the logs.<br />

2. Ensure that volumes are properly configured on the volume database host that<br />

matches the volume database host configured <strong>for</strong> the robot or set of standalone<br />

drives. Use tpconfig -d and tpconfig -lsavdbhost to list the configured<br />

volume database hosts. Select the current server (the one you are administering) to be<br />

the same as the host which is the correct volume database host <strong>for</strong> a targeted device.<br />

3. Update the volume or device configurations, specify the correct volume database<br />

host, modify volume properties, or adjust search criteria as needed so that the volume<br />

query can find a matching volume.<br />

Media Manager Status Code: 36<br />

Message: barcode not unique in database<br />

Explanation: A volume entry being added to or changed in the volume database had a<br />

barcode specified which was a duplicate of the barcode <strong>for</strong> another volume already in the<br />

volume database. All volumes in a volume database must have a unique barcode.<br />

Recommended Action:<br />

1. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error, as follows.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the volume daemon/<strong>NetBackup</strong><br />

Volume Manager service, or start vmd with the verbose option, if available.<br />

b. Retry the operation and examine the logs.<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!