NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
install_path\Volmgr\misc folder. Invoke tpunmount filename for each line in the
.ltisymlinks file, where filename specifies the contents of a line in that file. For
example, on UNIX, the command may look like the following:
tpunmount /usr/openv/netbackup/db/media/tpreq/A00001
Chapter 5, Media Manager Status Codes and Messages 321
Status Codes
Device Management Status Code: 21
Message: The drive is not ready or inoperable
Explanation: A drive was selected for a mount request, but the drive is not ready with
loaded media.
Recommended Action: Wait until the drive is ready before manually assigning a drive to
a pending mount request.
Device Management Status Code: 22
Message: IPC Error: Daemon may not be running
Explanation: A request to ltid could not be serviced. (ltid is the Media Manager
device daemon on UNIX or the NetBackup Device Manager service on Windows.) ltid is
probably not running. If ltid is still running, its process lock file may have been removed.
Also, message queues may not be functioning correctly on the system.
Recommended Action:
1. If ltid is not running, start ltid and try the operation again. On UNIX, run
/usr/openv/volmgr/bin/ltid, and on Windows, start the NetBackup Device
Manager service.
2. If ltid was already running, check for the existence and permissions of the lock file
itself and the lock file directory, which are /usr/openv/volmgr/misc/.ltipid
(UNIX) or Install_ path\Volmgr\misc\.ltipid (Windows). Terminate the ltid
process if it is running. Create the lock directory/folder and adjust the permissions as
needed so that ltid can obtain the above lock.
3. On UNIX, check the msgget man page and look for suggestions on troubleshooting
the system message queues.
Device Management Status Code: 23
Message: Invalid Drive Number
Explanation: A request was made for drive, but no such drive could be found in the active
configuration.
NetBackup 4.5 Troubleshooting Guide for Windows