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

2. On the UNIX host where the request originated, check the system group<br />

configuration and ensure that add/change pool requests include only valid group<br />

IDs. No validation is attempted <strong>for</strong> group IDs in volume pools on <strong>Windows</strong>.<br />

Media Manager Status Code: 129<br />

Message: invalid drive name<br />

Explanation: A request was made to register, reserve, or release a shared drive with<br />

vmd/DA (the device allocator <strong>for</strong> the Shared Storage Option), and the drive name was<br />

not correctly <strong>for</strong>matted.<br />

Recommended Action:<br />

1. Examine the daemon and reqlib debug logs <strong>for</strong> a more detailed message on the 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. Ensure that the drive name is from 1 to 48 ASCII characters in length. The following<br />

special characters are allowed: period (.), plus (+), minus (-), underscore (_).<br />

3. Verify that the correct version of software is running on all servers.<br />

Media Manager Status Code: 130<br />

Message: requested drive is already reserved<br />

Explanation: A request was made to reserve a shared drive with vmd/DA (the device<br />

allocator <strong>for</strong> the Shared Storage Option), and the drive was already reserved <strong>for</strong> another<br />

host.<br />

This is a normal occurrence when drive resources are being oversubscribed <strong>for</strong> either of<br />

these reasons: independent schedulers/applications accessing the same pool of drives, or<br />

hardware or media errors causing some drives allocated to jobs to become unavailable.<br />

Recommended Action:<br />

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