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

Recommended Action:<br />

1. Ensure that cleaning media has been added to the robotic library <strong>for</strong> each drive type<br />

capable of being cleaned with a separate cleaning cartridge.<br />

2. Ensure there is a positive number of cleanings available <strong>for</strong> the cleaning media in the<br />

appropriate volume database <strong>for</strong> the robotic library. Replace the cleaning tape or<br />

increase the number of cleanings <strong>for</strong> the cleaning media be<strong>for</strong>e the count reaches zero.<br />

3. Check the availability of vmd (the Media Manager volume daemon on UNIX or<br />

<strong>NetBackup</strong> Volume Manager service on <strong>Windows</strong>) on the volume database host<br />

where the cleaning media is defined, by sending a request to it or using a media<br />

management interface.<br />

4. Examine command output (if available), debug logs, and system logs <strong>for</strong> messages<br />

related to the error. 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 device daemon (ltid) on UNIX, or the <strong>NetBackup</strong><br />

Device Manager service on <strong>Windows</strong>.<br />

Device Management Status Code: 60<br />

Message: No robot daemon or robotics are unavailable<br />

Explanation: A robot was not configured or was operationally unavailable. Specifically,<br />

an attempt may have been made to automatically clean a robotic drive, but the robot is not<br />

defined or is unavailable. Alternatively, on an attempt to initialize the shared drive lists, a<br />

drive was found to be configured as robotic, without the required robot configured.<br />

Recommended Action: Display the device configuration and ensure that the drive and<br />

robotic configuration in<strong>for</strong>mation are consistent. Check the operational status of the robot<br />

and robotic software by checking the system log files. If more detail on robot operational<br />

status is needed, increase the level of verbosity by adding the VERBOSE option in the<br />

vm.conf file and restarting ltid (the device daemon / <strong>NetBackup</strong> Device Manager<br />

service).<br />

Device Management Status Code: 61<br />

Message: No media found in device or robot slot, please verify<br />

Explanation: On a request to mount media, no media was found in the targeted location<br />

be<strong>for</strong>e a designated time period had elapsed.<br />

Recommended Action: Resubmit the request, and mount the media in the targeted drive<br />

be<strong>for</strong>e the designated time period has elapsed. Check the device configuration to ensure<br />

that the correct drive name has been configured and that ltid, the device daemon, was<br />

restarted after the last device configuration change was made.<br />

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