NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 281
Status Codes
Media Manager Status Code: 166
Message: media access port not available
Explanation: A request was made to physically move a volume into or out of a robotic
library, but the media access port was found to be unavailable.
Recommended Action:
1. Examine command output (if available), debug logs, and system logs for a more
detailed message on the error.
a. If it is 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. Ensure that the physical move volume request for the robot type was not sent to a
robotic control daemon/process on a system running an older, incompatible version
of the software.
3. Ensure that the targeted robotic control daemon/process is operating normally.
Media Manager Status Code: 167
Message: ADAMM GUID is not unique in the database
Explanation: A volume entry being added to or changed in the volume database had an
ADAMM GUID specified which was a duplicate of the ADAMM GUID for another
volume already in the volume database. All volumes in a volume database must have an
ADAMM GUID that is either unique or null. (ADAMM is Advanced Device and Media
Management, and a GUID is a Global Unique Identifier.)
The GUID conflict may occur if the following are both true:
◆ The bephyinv.exe or beconv.exe command is running on a Windows host, in
install_path\NetBackup\bin\admincmd.
AND
◆ The GUID field of a record in the volume database is modified, by either adding,
changing, or deleting records.
Another possible cause may be one of the following:
◆ The physical inventory utility (bephyinv.exe) has already been run on this media.
NetBackup 4.5 Troubleshooting Guide for Windows