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

Explanation: A media management interface attempted to wait <strong>for</strong> a child process to<br />

complete, but unexpectedly found that there was no such child process to wait <strong>for</strong>.<br />

Recommended Action:<br />

Examine interface output and debug logs <strong>for</strong> a more detailed message error.<br />

1. If not already enabled, enable debug logging by creating the necessary<br />

directories/folders. Increase the level of verbosity by adding the VERBOSE option in<br />

the vm.conf file and restarting the daemons/services, or by executing the<br />

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

2. Retry the operation (or try using a different media management interface) and<br />

examine the logs.<br />

Media Manager Status Code: 65<br />

Message: volume group does not exist<br />

Explanation: While processing a request, a volume group could not be found within the<br />

existing volume entries in the volume 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. Check <strong>for</strong> data integrity or consistency problems in the volume database by using a<br />

media management interface or vmdb_dump. Delete or move volume entries so that<br />

the volume group issues are corrected.<br />

Media Manager Status Code: 66<br />

Message: no cleaning tape available<br />

Explanation: The volume database was queried <strong>for</strong> cleaning tapes by robot number. No<br />

cleaning tape in the specified robot with available cleanings remaining was found in the<br />

volume database.<br />

Recommended Action:<br />

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