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

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

Status Codes<br />

1. Examine the daemon debug log <strong>for</strong> a more detailed message on the system error, as<br />

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. The volume database may be corrupted. Restore an older volume database from a<br />

saved version or from catalog backups.<br />

Media Manager Status Code: 28<br />

Message: database read operation read too few bytes<br />

Explanation: vmd (the Media Manager volume daemon on UNIX or <strong>NetBackup</strong> Volume<br />

Manager service on <strong>Windows</strong>) encountered a record that was smaller than expected while<br />

reading a volume database record.<br />

Recommended Action:<br />

1. Examine the daemon debug log <strong>for</strong> a more detailed message on the system error, as<br />

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. The volume database may be corrupted. Restore an older volume database from a<br />

saved version or from catalog backups.<br />

Media Manager Status Code: 29<br />

Message: database lock operation failed<br />

Explanation: vmd (the Media Manager volume daemon on UNIX) encountered a system<br />

call error while attempting to lock the volume database. This error code applies to UNIX<br />

servers only.<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!