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.

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 the daemon debug log <strong>for</strong> a more detailed message on the system 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 volume daemon, or start vmd with<br />

the verbose option.<br />

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

2. Obtain the specific system call failure from the debug log, and investigate operating<br />

system functionality related to the failure.<br />

Media Manager Status Code: 60<br />

Message: cannot per<strong>for</strong>m operation on this host<br />

Explanation: A requested operation is not functional on a particular host.<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. Device discovery must be invoked only on specific plat<strong>for</strong>ms where it is supported.<br />

Robot inventory update, with optical media <strong>for</strong>matting specified, must be invoked<br />

only on the host where the robotic control and optical drives are configured.<br />

Media Manager Status Code: 61<br />

Message: robot number and robot host mismatch<br />

Explanation: A request was made to add or change volumes in the volume configuration,<br />

or to issue a robot inventory update request. A robot host was specified that differed from<br />

the robot host <strong>for</strong> other volumes in the same robot (defined as those volumes having the<br />

same robot number). All volumes in the volume database that have a given robot number<br />

(<strong>for</strong> instance, 0) must have the same robot host name.<br />

Recommended Action:<br />

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