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

Media Manager Status Code: 100<br />

Message: the requested slot is empty<br />

Explanation: A request was made to validate/update the barcode <strong>for</strong> a volume, and<br />

in<strong>for</strong>mation from the robot indicated that there was no volume in the robot that used the<br />

requested slot <strong>for</strong> its home location.<br />

Recommended Action:<br />

The volume configuration is not consistent with the physical contents of the robotic<br />

library that is associated with the volume. The volume configuration or media placement<br />

in the robotic library needs to be adjusted using one of the media management interfaces.<br />

Update/validate barcode requests are made <strong>for</strong> each volume affected whenever a volume<br />

configuration is added or changed. Volume entries are still changed when the<br />

update/validate step fails, so administrative steps are required to ensure that volume<br />

entries are defined only <strong>for</strong> media slots in the library where the correct media resides. For<br />

media located in drives at the time the update/validate barcode is tried, the robotic<br />

in<strong>for</strong>mation will relate the media with its known home slot location.<br />

Media Manager Status Code: 101<br />

Message: media type and volume group mismatch<br />

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

volume configuration, and the media type and volume group associated with the volume<br />

configuration changes are in conflict with the requirements <strong>for</strong> volume groups. All<br />

volumes in a volume group are required to have the same residence, which includes<br />

having the same media type. Media types used <strong>for</strong> data and their associated cleaning<br />

media types are considered as being the same media types with regard to volume group<br />

restrictions.<br />

Recommended Action:<br />

1. Examine command output (if available), debug logs, and system logs <strong>for</strong> a more<br />

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 daemons/services, or by executing<br />

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

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

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