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

Status Codes<br />

Explanation: On a request to assign, reserve, or scan a drive, the targeted device host<br />

determined that it was not the scan host <strong>for</strong> the drive, so the request was refused (to be<br />

retried by the caller).<br />

Recommended Action:<br />

1. If problems are encountered as a result of the reported error, check <strong>for</strong><br />

communication, configuration, and system problems among the associated hosts.<br />

Display the device configurations on the affected hosts to determine the role that each<br />

host is handling <strong>for</strong> drive sharing. Identify the DA (drive allocation) host as the<br />

volume database <strong>for</strong> the residence in which the drives are configured. Identify the<br />

current scan host <strong>for</strong> the drive by sending a vmdareq call to the DA host.<br />

2. Examine command output (if available), debug logs, and system logs <strong>for</strong> messages<br />

related to the error. Enable debug logging by creating the necessary<br />

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

the vm.conf file and restarting ltid (the device daemon on UNIX or <strong>NetBackup</strong><br />

Device Manager service on <strong>Windows</strong>). Configure scan ability priorities <strong>for</strong> assigning<br />

scan hosts by changing the Media Manager configuration, so that less network<br />

connections need to be maintained, and greater system load is placed on hosts more<br />

capable of servicing the load.<br />

Device Management Status Code: 49<br />

Message: Tape file path exceeds 255 character maximum<br />

Explanation: On a tape mount request, the file name associated with the request exceeded<br />

255 characters.<br />

Recommended Action: When requesting a tape mount, ensure that the file name does not<br />

exceed 255 ASCII characters in length. If the mount requests are coming from an<br />

application, request an application change to use a shorter file name, or if needed, install<br />

the product in a directory/folder that will not cause the file name limit to be exceeded.<br />

Device Management Status Code: 50<br />

Message: No action pending <strong>for</strong> given mount index<br />

Explanation: On a request to obtain the pending action <strong>for</strong> a mount request, there was no<br />

known pending action associated with the request.<br />

Recommended Action: Use a device monitor interface to display requests that have<br />

pending actions. Per<strong>for</strong>m requests (like assign, deny, display, or resubmit) only on<br />

requests that have pending actions.<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!