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.

<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 349<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. Investigate the state of the physical hardware and correct the holder status <strong>for</strong><br />

storage, drive, and transport elements as needed. Then, resubmit the request.<br />

Robotic Status Code: 223<br />

Message: Robot busy, cannot per<strong>for</strong>m operation<br />

Explanation: The robot is busy per<strong>for</strong>ming another operation, using resources needed <strong>for</strong><br />

the requested operation.<br />

Recommended Action: Wait until the robot is done per<strong>for</strong>ming current external-based<br />

requests (including robot inventory and inject/eject media) be<strong>for</strong>e starting new requests.<br />

Check vendor or operating system administrative interfaces and logs to see if robotic<br />

resources are busy.<br />

Robotic Status Code: 224<br />

Message: Control daemon connect or protocol error<br />

Explanation: A protocol error occurred between robotic and other components.<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. Resolve the situation by referring to troubleshooting methods or investigating the<br />

system log messages related to the specific error leading to the media mount failure.<br />

Verify that all Media Manager binaries are at a compatible version level.<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!