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 (if available), debug logs, and system logs <strong>for</strong> messages<br />

related to the error.<br />

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

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

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

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

2. On UNIX servers, gather output from the ipcs -a command to see what resources<br />

are currently in use.<br />

Device Management Status Code: 4<br />

Message: Error in Receiving Operator Message<br />

Explanation: An attempt was made to receive a message from ltid (the Media Manager<br />

device daemon on UNIX and the <strong>NetBackup</strong> Device Manager service on <strong>Windows</strong>) on an<br />

already existing internal message queue used <strong>for</strong> inter-process communication. But an<br />

error was encountered in the message communications. The error probably indicates a<br />

lack of system resources <strong>for</strong> message queues.<br />

Recommended Action:<br />

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

related to the error.<br />

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

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

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

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

2. On UNIX servers, gather output from the ipcs -a command to see what resources<br />

are currently in use. Investigate whether ltid is tied up in communications with<br />

devices or other components.<br />

Device Management Status Code: 5<br />

Message: Error in Sending Daemon Message<br />

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