NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
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. One of the following may have
occurred, as described in the following steps.
3. Lock file problems: The device discovery process sets a lockfile in the
/usr/openv/volmgr/misc (UNIX) or Install_path\Volmgr\misc (Windows)
directory named tpac.lock to ensure that only one instance of discovery is running
on a particular host. It then checks the lockfile before updating the configuration.
◆ Cannot obtain lockfile.
The lockfile may be held by another discovery process. In this case the following
error is displayed:
"another tpautoconf is already running"
Use standard OS process tools (ps on UNIX or Task Manager on Windows) to
determine if another tpautoconf process is running. If not, delete the lockfile
and re-run device discovery. If another tpautoconf process is running, wait for
it to complete before retrying.
◆ Failed checking lockfile.
In the case of long device-discovery cycles, the interface may timeout or the user
may cancel the process. Part of the timeout or cancelling is to remove the lockfile.
This tells the device discovery process that it should not continue making
modifications to the device configuration. If this happens, re-run the discovery
process.
4. Global device database inconsistency: Prior to beginning the process of discovering
new devices on a host, the global device database is checked for internal consistency.
The following are example log messages in the tpcommand log directory, along with
steps to determine the problem and correct it.
◆ Fatal Global Database consistency error: Couldn’t contact robot 1 on host mud
The global device database has found a robot entry for robot 1 on mud, but could
not communicate with it. Delete that robot on host mud and re-run device
discovery there.
◆ Fatal Global Database consistency error: TLM/ACS control host mismatch 1 on
hosts bison and mud.
300 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows