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

Recommended Action: If problems are encountered as a result of the reported error,<br />

verify that there are no unexpected robotic daemons/processes running by executing<br />

vmps. Stop and restart ltid (the Media Manager device daemon on UNIX or the<br />

<strong>NetBackup</strong> Device Manager service on <strong>Windows</strong>) so that its internal tables are<br />

re-initialized.<br />

Device Management Status Code: 46<br />

Message: Tape needs to be write enabled<br />

Explanation: On a tape mount request, the specified access mode was <strong>for</strong> write access, but<br />

the physical media was write-protected.<br />

Recommended Action: Change the physical media write-protect setting to allow write<br />

access (unlocked), or resubmit the request with read-only access. To request read-only<br />

access using tpreq, specify an access mode argument of r <strong>for</strong> read or use the default<br />

(read) access mode.<br />

Device Management Status Code: 47<br />

Message: Unable to establish scan host <strong>for</strong> shared drive<br />

Explanation: On a request to change a shared drive’s status, an attempt to establish a<br />

connection to the drive’s scan host failed.<br />

Recommended Action:<br />

1. Determine which host is serving as the drive’s scan host. Do this by sending a<br />

vmdareq command to the volume database host <strong>for</strong> the drives’s residence (robot or<br />

set of standalone drives on a host).<br />

2. Ensure that vmd (the Media Manager volume daemon on UNIX or <strong>NetBackup</strong><br />

Volume Manager service on <strong>Windows</strong>) is running on the scan host. On the scan host,<br />

examine debug logs and system logs <strong>for</strong> messages related to the error.<br />

3. Enable debug logging by creating the necessary directories/folders. Increase the level<br />

of verbosity by adding the VERBOSE option in the vm.conf file and restarting ltid (the<br />

device daemon on UNIX or <strong>NetBackup</strong> Device Manager service on <strong>Windows</strong>). The<br />

detailed reason <strong>for</strong> the canceled request should be available in the daemon debug logs<br />

on the scan host. Correct the problem and resubmit the request if needed.<br />

Device Management Status Code: 48<br />

Message: Host is not the scan host <strong>for</strong> this shared drive<br />

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