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

Media Manager Status Code: 42<br />

Message: cannot connect to robotic software daemon<br />

Explanation: A connection to a robotic software daemon/process could not be<br />

established. This can occur when a process tries to connect to the robotic process that is<br />

not running. It can also occur if the network or server is heavily loaded and has slow<br />

response time.<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 volume daemon/<strong>NetBackup</strong><br />

Volume Manager service, or start vmd with the 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.<br />

3. Verify that the robotic process used <strong>for</strong> robotic control is available (see table “Media<br />

Manager Daemons and Programs” on page 459), and start the robotic process if<br />

necessary.<br />

4. Ensure that there is only one configured robot control host <strong>for</strong> each LMF, TL8, TLD,<br />

and TLH robot and that all volumes in the volume configuration have a robot host<br />

that matches the configured robot control host.<br />

5. Change the volumes or reconfigure the robot in the device configuration as needed.<br />

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

processing requests during the time when connections to it are attempted.<br />

Media Manager Status Code: 43<br />

Message: failed sending to robotic software daemon<br />

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

failed.<br />

Recommended Action:<br />

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