NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
1. Examine command output (if available) and debug logs 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 daemons/services, or execute the
command’s verbose option, if available.
b. Retry the operation and examine the logs.
2. Investigate the integrity of the file system and global device database,
/usr/openv/volmgr/database/globDB (UNIX) or Install_
path\Volmgr\database\globDB (Windows).
Media Manager Status Code: 155
Message: global device database append operation failed
Explanation: A request was made to change the device configuration, and a global device
database record could not be written to the global device database file.
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 / NetBackup
Volume Manager service, or start vmd with the verbose option.
b. Retry the operation and examine the logs.
2. Examine the permissions and available file system space for writing to the database,
/usr/openv/volmgr/database/globDB (UNIX) or
install_path\Volmgr\database\globDB (Windows).
Media Manager Status Code: 156
Message: global device database lock operation failed
Explanation: vmd, the Media Manager volume daemon (UNIX), encountered a system
call error while attempting to lock the global device database.
Recommended Action:
276 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows