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 />

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.<br />

b. Retry the operation and examine the log files.<br />

Device Configuration Status Code: 15<br />

Chapter 5, Media Manager Status Codes and Messages 291<br />

Status Codes<br />

Message: Invalid robot number<br />

Explanation: On a request to modify the device configuration, the specified robot number<br />

was not within the allowable range, or the robot number did not correspond to a currently<br />

configured robot, or the robotic database is corrupted.<br />

Recommended Action:<br />

1. Specify a robot number in the range of 0 to 32767.<br />

2. Ensure that all device configuration changes or deletions are per<strong>for</strong>med on devices<br />

that are currently part of the device configuration.<br />

3. Check the integrity of the robotic database file robotic_def located in the directory<br />

/usr/openv/volmgr/database (UNIX) or the folder<br />

install_path\Volmgr\database (<strong>Windows</strong>), by displaying the contents of the device<br />

configuration. Restore a saved copy of the robotic database from catalog backups, or<br />

delete it and recreate any needed robotic configuration in<strong>for</strong>mation.<br />

Device Configuration Status Code: 16<br />

Message: A SCSI inquiry sent to the device has failed<br />

Explanation: On a request to add or update a SCSI robotic library or drive, Media<br />

Manager failed to obtain the serial number and inquiry string <strong>for</strong> the device. This<br />

in<strong>for</strong>mation is obtained by Media Manager by sending a SCSI Inquiry command to the<br />

device. Failure indicates that <strong>NetBackup</strong> was not able to communicate with the device by<br />

means of SCSI.<br />

Recommended Action:<br />

1. Ensure that the device is physically connected.<br />

2. Ensure that the operating system is configured to recognize the device and that the<br />

operating system can see the device.<br />

3. Ensure that no other process is using the device and that the device is not offline.<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!