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

Status Codes<br />

Either add cleaning tapes to the robot (physically, and logically in the volume database<br />

with a media management interface), or change the number of allowed cleanings if a<br />

cleaning tape is already configured and the cleaning tape is to be used beyond its<br />

allocated use cycles. Then reissue the cleaning request, or wait <strong>for</strong> the cleaning request to<br />

be automatically submitted when a drive in the robot once again needs cleaning.<br />

Media Manager Status Code: 67<br />

Message: unable to send exit status<br />

Explanation: vmd could not send the status of a requested operation to the requestor. (vmd<br />

is the Media Manager volume daemon on UNIX and the <strong>NetBackup</strong> Volume Manager<br />

service on <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, or start vmd with<br />

the verbose option.<br />

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

2. Obtain the specific send or write system call failure from the debug log, and<br />

investigate operating system functionality related to the failure.<br />

3. Check to see whether the command or application interface sending the request is<br />

aborting prematurely, as follows: enable reqlib debug logs, retry the operation, check<br />

the debug logs, and observe application interface output.<br />

Media Manager Status Code: 68<br />

Message: too many volumes in volume group<br />

Explanation: A request was made to add or change volumes in the volume configuration,<br />

and the limit <strong>for</strong> the allowed number of volumes in a volume group was reached. The<br />

limit <strong>for</strong> the number of volumes in a volume group is based on the number of volumes<br />

allowed in a particular type of robot.<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!