NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 241
Status Codes
1. Examine command output (if available), debug logs, and system logs for a more
detailed message on the error.
a. If not already enabled, enable debug logging by creating the necessary
directories/folders. Increase the level of verbosity by adding the VERBOSE
option in the vm.conf file and restarting the daemons/services, or by executing
the command’s verbose option, if available.
b. Retry the operation and examine the logs.
2. Ensure that volumes are properly configured on the volume database host that
matches the volume database host configured for the robot or set of standalone
drives. Use tpconfig -d and tpconfig -lsavdbhost to list the configured
volume database hosts. Select the current server (the one you are administering) to be
the same as the host which is the correct volume database host for a targeted device.
Update the volume or device configurations, target the correct volume database host,
modify volume properties, or adjust search criteria as needed so that the volume
residence query can find a matching volume.
Media Manager Status Code: 81
Message: robot type and volume group mismatch
Explanation: A request was made to add volumes or change volume residences in the
volume configuration, and the robot type and volume group associated with the volume
configuration changes are in conflict with the requirements for volume groups. All
volumes in a volume group are required to have the same residence, which includes
having the same robot type. A requested operation may have tried to associate the special
No Volume Group name “---” with a robotic residence.
Recommended Action:
1. Examine command output (if available), debug logs, and system logs for a more
detailed message on the error.
a. If not already enabled, enable debug logging by creating the necessary
directories/folders. Increase the level of verbosity by adding the VERBOSE
option in the vm.conf file and restarting the daemons/services, or by executing
the command's verbose option, if available.
b. Retry the operation and examine the logs.
2. Ensure that the specified robot residence and volume group are compatible with
other volumes in the volume configuration that are in the specified volume group. Do
not try to move volumes in the special No Volume Group name “----” to a robotic
NetBackup 4.5 Troubleshooting Guide for Windows