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.

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 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 volume daemon, or start vmd with<br />

the verbose option, if available.<br />

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

2. Execute vmps to ensure that vmd and vmdb_dump are not both running at the same<br />

time.<br />

3. Ensure that no other process has a lock on the database file<br />

/usr/openv/volmgr/database/volDB.<br />

Media Manager Status Code: 30<br />

Message: database seek operation failed<br />

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

Manager service on <strong>Windows</strong>) encountered a read error while seeking (positioning)<br />

within the volume database.<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: 31<br />

Message: database unlock operation failed<br />

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

call error while attempting to unlock the volume database.<br />

Recommended Action:<br />

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