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

Recommended Action:<br />

1. Examine the daemon debug log <strong>for</strong> a more detailed message on the system 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 volume daemon/<strong>NetBackup</strong> Volume<br />

Manager service, or start vmd with the verbose option.<br />

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

2. Examine the permissions and available file system space <strong>for</strong> writing to the database:<br />

on UNIX, /usr/openv/volmgr/database/poolDB; on <strong>Windows</strong>,<br />

install_path\Volmgr\database\poolDB.<br />

Media Manager Status Code: 105<br />

Message: poolname is not unique in pool database<br />

Explanation: A request was made to add a volume pool in the volume pool configuration,<br />

but the pool name specified was a duplicate of the name <strong>for</strong> an existing volume pool.<br />

Recommended Action: On the add volume pool request, specify a volume pool name that<br />

is not already in use on the targeted volume database host.<br />

Media Manager Status Code: 106<br />

Message: pool 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 pool database.<br />

Recommended Action:<br />

1. Examine the daemon debug log <strong>for</strong> a more detailed message on the system 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 volume daemon, or start vmd with<br />

the verbose option.<br />

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

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

the same time.<br />

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