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.

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

Status Codes<br />

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

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

2. When using robot inventory update to make changes to the volume configuration,<br />

ensure that all volumes of the same physical cartridge type (<strong>for</strong> example, 3590J in TLH<br />

robots) are mapped to a single media type, such as HCART. This ensures that all<br />

media in the robotic library can be mounted on drives with a compatible drive type.<br />

3. When assigning volumes manually, specify the media type associated with the<br />

volume. Check the device configuration to determine if the volume database host <strong>for</strong><br />

the device is consistent with the volume configuration in the volume database.<br />

Applications may attempt to query multiple volume databases <strong>for</strong> volume-related<br />

requests, so ensure that duplicate media IDs are not used in volume configurations<br />

across multiple hosts. If duplicate IDs are found, either completely separate the<br />

configurations by not sharing any devices, or remove volumes with duplicate media<br />

IDs and consolidate volumes into one volume configuration. Always use barcodes<br />

that are unique with respect to the six (6) least significant characters across all media<br />

in all robots, or use media ID generation rules to ensure unique media IDs are<br />

generated when using robot inventory update.<br />

Media Manager Status Code: 96<br />

Message: oprd returned abnormal status<br />

Explanation: A request serviced by oprd (the operator request daemon/process) or by<br />

rdevmi (the remote device management interface) returned an abnormal status.<br />

Recommended Action:<br />

1. On <strong>Windows</strong>, when auto-configuring devices or initiating the <strong>NetBackup</strong> Device<br />

Manager service from a graphical or command line interface, ensure that the service<br />

has not been disabled in the system services configuration.<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!