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

Status Codes<br />

1. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error, as follows.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the daemons/services, or by executing<br />

the command’s verbose option, if available.<br />

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

2. Identify the robotic process by looking at the robot type, and at the robot host on the<br />

robotic request or the robot host field of the volume being operated on. Verify that the<br />

robotic process used <strong>for</strong> robotic control is available and handling requests (see table<br />

“Media Manager Daemons and Programs” on page 459).<br />

3. Identify the robot control host by checking the device configuration. There should be<br />

only one configured robot control host <strong>for</strong> each LMF, TL8, TLD, and TLH robot and<br />

all volumes in the volume configuration should have a robot host that matches the<br />

configured robot control host.<br />

4. Check the system log on the robot control host to see if the robotic process is<br />

processing requests during the time when communications with it are attempted.<br />

Per<strong>for</strong>m “Resolving Network Communication Problems” on page 21.<br />

Media Manager Status Code: 44<br />

Message: failed receiving from robotic software daemon<br />

Explanation: An attempt to read data from a robotic software daemon/process socket<br />

failed.<br />

Recommended Action:<br />

1. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error, as follows.<br />

a. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE<br />

option in the vm.conf file and restarting the daemons/services, or by executing<br />

the command's verbose option, if available.<br />

b. Retry the operation and examine the logs.<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!