NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 277
Status Codes
1. Examine the daemon debug log for a more detailed message on the system 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 volume daemon, or start vmd with
the verbose option.
b. Retry the operation and examine the logs.
2. Ensure that no other process has a lock on the global device database file
/usr/openv/volmgr/database/globDB.
Media Manager Status Code: 157
Message: global device database open operation failed
Explanation: A requested operation encountered a situation where the global device
database file could not be opened.
Recommended Action:
1. Check for the existence and permissions of the globDB file in the
/usr/openv/volmgr/database directory or install_path\Volmgr\database
folder.
2. Restore the globDB file from the catalog backups or from another location, change the
access permissions on the existing globDB, or (as a last resort) move/rename the
current globDB to start over with an empty global device configuration.
3. If the move/rename method is used, recreate all device configurations on all hosts.
Media Manager Status Code: 158
Message: global device database close operation failed
Explanation: An error occurred when vmd attempted to close the global device database.
Recommended Action: Examine the daemon debug log for a more detailed message on
the system error.
1. 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 volume daemon / NetBackup Volume Manager
service, or start vmd with the verbose option.
2. Retry the operation and examine the logs.
NetBackup 4.5 Troubleshooting Guide for Windows