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

Status Codes<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. Issue a robot inventory Contents report to obtain the list of media in the robotic<br />

library. Check to see whether inventory filters have been enabled in the Media<br />

Manager configuration file, since they affect the contents of the media list returned<br />

from the robotic daemon/process. Use a robot test utility or an operating<br />

system/vendor administrative interface to verify the status of media, as needed.<br />

Update the volume configuration and search <strong>for</strong> the media if it was not in the robotic<br />

library, as needed, and resubmit the request.<br />

Robotic Status Code: 233<br />

Message: Volume is in library, but not in drive domain<br />

Explanation: The media was found in the robotic library, in a domain of the library that is<br />

inaccessible to the drives that are configured in the robot.<br />

Recommended Action: Issue a robot inventory Contents report to obtain the list of media<br />

in the robotic library. Check the device configuration and ensure that the drive addresses<br />

correspond to the correct domain <strong>for</strong> the media. Correct the device configuration as<br />

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

service on <strong>Windows</strong>). Use a robot test utility or a vendor administrative interface to verify<br />

the status of media, as needed. Update the volume configuration and physically move the<br />

media into the robotic library, as needed, and resubmit the request.<br />

Robotic Status Code: 234<br />

Message: Robot denied access to the resource<br />

Explanation: The media was found in the robotic library, but is being denied access<br />

according to an established security policy.<br />

Recommended Action: Issue a robot inventory Contents report to obtain the list of media<br />

in the robotic library. Use a vendor administrative interface to verify the status of media,<br />

as needed. Delete the media in the volume configuration, or make the volume accessible<br />

through a vendor administrative interface, as appropriate. Update the volume<br />

configuration, as needed, and resubmit the request.<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!