NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
◆ This media had on-disk Backup Exec catalogs, and the catalog converter utility
(beconv.exe) has already been run on this media.
Recommended Action:
1. Examine command output (if available) and the daemon and reqlib 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. From the daemon debug log file, determine the offset of the volume that has an
ADAMM GUID conflict with the volume entry that is being added or changed. (The
offset is the index of the volume in the volume database.) Using the vmdb_dump
command, dump out all volume records in the volume configuration for the targeted
volume database host and look up the volume offset indicated in the debug log file.
Note the associated ADAMM GUID, which is the field adamm_guid.
Note Although a GUID can be changed or added by means of the vmchange and vmadd
commands, the GUID field is for internal use only. Do not add or change a GUID.
Media Manager Status Code: 168
Message: ADAMM GUID does not exist in database
Explanation: The volume database was queried for a specified ADAMM (Advanced
Device and Media Management) GUID, and no volumes were found matching the
specified criteria. (The GUID is a Global Unique Identifier.)
This error could result if both of the following occur:
◆ The bephyinv.exe command 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.
Recommended Action:
282 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows