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

Robotic Status Code: 208<br />

Message: Requested slot is empty<br />

Explanation: No media was found in a specified slot. The volume configuration may not<br />

be consistent with the physical contents of the robotic library that is associated with the<br />

volume.<br />

Recommended Action: Install or realign the container/holder <strong>for</strong> the media if it was<br />

missing or misaligned. Place media right-side-up in the slot if the media is upside-down.<br />

Check to see if the requested slot is reserved to the robotic library <strong>for</strong> internal use.<br />

Physically correct issues within the robotic library, or use a media management interface<br />

to correct the volume configuration.<br />

Robotic Status Code: 209<br />

Message: Unable to open drive<br />

Explanation: The drive could not be opened. The drive configuration may be incorrect<br />

and the drive may be logically DOWN. Also, the drive may never have become ready<br />

after media was placed in the drive.<br />

Recommended Action:<br />

1. Examine command output (if available), debug logs, and system logs <strong>for</strong> messages<br />

related to the error.<br />

a. Enable debug logging by creating the necessary directories/folders. Increase the<br />

level of verbosity by adding the VERBOSE option in the vm.conf file and<br />

restarting ltid (the device daemon on UNIX or <strong>NetBackup</strong> Device Manager<br />

service on <strong>Windows</strong>).<br />

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

2. Check <strong>for</strong> improperly configured cleaning media or interference with the drive<br />

cleaning operation. Check <strong>for</strong> bad media which may have led to the drive not<br />

becoming ready after media was placed within it.<br />

3. To avoid configuring incorrect device paths and device names, which is a common<br />

root cause of drive open problems, use the Device Configuration wizard (on<br />

supported device discovery plat<strong>for</strong>ms) so that device paths and device names can be<br />

automatically configured. Resolve the situation by referring to troubleshooting<br />

methods or investigating the system log messages related to the specific error leading<br />

to the open failure.<br />

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