NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 259
Status Codes
1. Examine command output (if available) and debug 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 execute the
command’s verbose option, if available.
b. Retry the operation and examine the logs.
2. Change the volume expiration date to a future date in relation to the current system
date/time if you want to extend the active life of the physical media. Alternatively,
replace the media with other media that still has useful life remaining. Check the
system date/time and reset it correctly as needed.
3. If the media expiration is already set to a future date as compared to the current
system date, check the device configuration to determine if the volume database host
for the device is consistent with the volume configuration in the volume database.
Applications may attempt to query multiple volume databases for volume-related
requests, so ensure that duplicate media IDs are not used in volume configurations
across multiple hosts. If duplicate IDs are found, either completely separate the
configurations by not sharing any devices, or remove volumes with duplicate media
IDs and consolidate volumes into one volume configuration. Always use barcodes
that are unique with respect to the six (6) least significant characters across all media
in all robots, or use media ID generation rules to ensure unique media IDs are
generated when using robot inventory update.
Media Manager Status Code: 116
Message: volume has exceeded maximum mounts
Explanation: A request was made to assign a volume, and the volume’s number of
mounts has exceeded the maximum number of mounts allowed for the volume (or the
maximum number allowed for the volume partner, in the case of optical media).
Recommended Action:
1. Examine command output (if available) and debug 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 execute the
command’s verbose option, if available.
b. Retry the operation and examine the logs.
NetBackup 4.5 Troubleshooting Guide for Windows