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

5. Check the system log on the robot control host <strong>for</strong> errors logged by the robotic<br />

software.<br />

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

Status Codes<br />

Media Manager Status Code: 47<br />

Message: no entries changed<br />

Explanation: A requested operation was completed, but no changes to the volume<br />

configuration or Media Manager configuration file were made. The administrator may<br />

have aborted an operation instead of continuing with proposed changes, or the<br />

configuration file may have already included the configuration entry that was being<br />

added.<br />

Recommended Action:<br />

1. No action is needed if the administrator aborted the change operation.<br />

2. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message 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 />

Media Manager Status Code: 48<br />

Message: no entries deleted<br />

Explanation: A delete volume(s) operation completed, but no changes were made to the<br />

volume configuration.<br />

Recommended Action:<br />

1. No action is needed, unless volumes that were requested to be deleted were not in fact<br />

deleted.<br />

2. Examine command output (if available) and the daemon and reqlib debug logs <strong>for</strong> a<br />

more detailed message on the error, as follows.<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!