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

Status Codes<br />

Recommended Action: In the <strong>NetBackup</strong> Media Manager System Administrator’s <strong>Guide</strong><br />

appendices, check the Robot Attributes tables to determine valid media types <strong>for</strong> a given<br />

robot type. Drive types directly correspond to the listed media types. Configure<br />

supported devices so that invalid combinations of drive types and robot types are not<br />

required.<br />

Device Configuration Status Code: 28<br />

Message: Invalid robot drive number <strong>for</strong> the robot type<br />

Explanation: On a request to configure a drive to be in a robot, it was found that the robot<br />

drive number was not valid <strong>for</strong> the selected robot type.<br />

Recommended Action: The robot drive number, or <strong>for</strong> ACS robots the set of ACS drive<br />

identifiers, is limited to certain ranges based on the robot type. These limits are based on a<br />

supported device list. An invalid robot drive number means that the drive number was<br />

not within the acceptable range. Make sure that the robot hardware is supported and that<br />

the required patches are installed to support the robotic library. If the robot type is TLH or<br />

TLM, do not specify a robot drive number, because the drives are addressed using a<br />

vendor drive name.<br />

Device Configuration Status Code: 29<br />

Message: Drive index is in use by another drive<br />

Explanation: On a request to add a drive to the device configuration, the requested drive<br />

index was found to be in use on the targeted device host.<br />

Recommended Action:<br />

1. To avoid configuring a drive index that is already in use, use the Device<br />

Configuration wizard (on supported device discovery plat<strong>for</strong>ms) so that the drive<br />

index is automatically configured.<br />

2. If using a device configuration interface that allows the drive index to be specified,<br />

use tpconfig -d to determine the drive indexes that are already in use on the<br />

targeted device host, and specify a drive index that is not already in use.<br />

Device Configuration Status Code: 30<br />

Message: Robot number is in use by another robot<br />

Explanation: On a request to add or update a robotic drive in the device configuration, it<br />

was found that the robot number and robot type specified were associated with an<br />

existing robot of a different robot type.<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!