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

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

detailed message on the error.<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. Check to see if volumes are defined in the volume database associated with a slot<br />

number zero that may not exist in the robot. Run a robot inventory Show contents of<br />

robot report and observe the starting slot number. If the starting slot number is one (1)<br />

and there is a volume defined in the robot at slot zero (0), delete the volume entry or<br />

move it to standalone so that the remaining available media slots can be utilized.<br />

Media Manager Status Code: 69<br />

Message: failed sending request to vmd<br />

Explanation: A request could not be sent to vmd or to oprd, even though the initial<br />

connection to the server process was successful. (vmd is the Media Manager volume<br />

daemon on UNIX or <strong>NetBackup</strong> Volume Manager service on <strong>Windows</strong>, and oprd is the<br />

operator request daemon/process.)<br />

Recommended Action:<br />

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

detailed message on the error.<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. Check to see whether the vmd or oprd process continued to run once it received the<br />

connection from the requestor. Run netstat -a or an equivalent socket diagnostic<br />

utility. Look at the daemon debug log on the server-side system and the process<br />

status of vmd/oprd to see if the server process is hung up.<br />

Media Manager Status Code: 70<br />

Message: cannot connect to vmd [on host host name]<br />

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