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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Status Codes<br />

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

Recommended Action: Check the device configuration on the targeted device host and<br />

identify the configured robots. On the drive configuration request, specify both the robot<br />

number and robot type that relate to the robot containing the drive.<br />

Device Configuration Status Code: 31<br />

Message: Robot number does not exist<br />

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

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

configured robots on the targeted device host.<br />

Recommended Action: Check the device configuration on the targeted device host and<br />

identify the configured robots. Every drive that is configured as a robotic drive must<br />

already have its robot configured on that device host. For shared robotic libraries having<br />

robotic control on a remote host, there must be a logical robotic entry that refers to the<br />

remote host having robotic control. Add the robot to the device configuration first, then<br />

add the drive, defining it to be in the robot. If the robot was already configured, specify<br />

the correct robot number and robot type on the drive or robot configuration request.<br />

Device Configuration Status Code: 34<br />

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

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

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

Recommended Action:<br />

1. To avoid configuring paths that are already in use, use the Device Configuration<br />

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

automatically configured.<br />

2. Be<strong>for</strong>e making configuration changes, check the existing drive configuration through<br />

a device configuration interface or run tpconfig -d to determine the drive paths<br />

that are already in use on the targeted device host, and specify a drive path that is not<br />

already in use.<br />

Device Configuration Status Code: 35<br />

Message: Drive name does not exist<br />

Explanation: On a request to update or delete a drive in the device configuration, no<br />

drives having the specified drive name were found on the targeted device host.<br />

Recommended Action: Check the device configuration on the targeted device host and<br />

identify the configured drives. When making drive configuration changes or deletions,<br />

specify the drive name as it is configured, taking care to use the proper case.<br />

296 <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!