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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Recommended Action:<br />

Chapter 5, Media Manager Status Codes and Messages 279<br />

Status Codes<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 execute the<br />

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

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

2. Identify the targeted host and verify that all Media Manager binaries on that host are<br />

at a compatible version level with other hosts that are part of the configuration.<br />

Update the software version as needed.<br />

Media Manager Status Code: 161<br />

Message: the global device database device serial number is invalid<br />

Explanation: An invalid or missing device serial number was encountered in a request to<br />

modify the device configuration.<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 execute the<br />

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

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

2. Identify the targeted host and verify that all Media Manager binaries on that host are<br />

at a compatible version level with other hosts that are part of the configuration.<br />

Update the software version as needed.<br />

Media Manager Status Code: 162<br />

Message: the global device database device name is invalid<br />

Explanation: An invalid or missing device name was encountered in a request to modify<br />

the device configuration.<br />

Recommended Action:<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!