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 command output, debug logs, and system logs <strong>for</strong> a more detailed message<br />

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 daemons/services, or by executing<br />

the command’s verbose option, if available.<br />

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

2. Identify the target components (<strong>for</strong> example, vmd and robotic processes on local or<br />

remote hosts) and verify that all Media Manager binaries are at compatible version<br />

level.<br />

Media Manager Status Code: 7<br />

Message: daemon terminated<br />

Explanation: The process is inactive or is terminating (or has terminated) from an event or<br />

signal, or as a direct result of a request from an authorized user or process.<br />

Recommended Action: If the targeted product component is needed but has terminated,<br />

restart the daemons/services on the targeted host.<br />

Media Manager Status Code: 8<br />

Message: invalid media ID<br />

Explanation: A process per<strong>for</strong>ming a media-related operation encountered an empty or<br />

incorrectly <strong>for</strong>matted media identifier, or was passed a media ID that could not be<br />

operated on as requested.<br />

Recommended Action:<br />

1. Examine command output and debug logs <strong>for</strong> a more detailed message on the error,<br />

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 daemons/services, or by executing<br />

the command’s verbose option, if available.<br />

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

2. Ensure that the media ID, where requested, is not blank.<br />

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