Symantec NetBackup Device management status code 21 to status code 25
Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases, Oracle, MySQL, Sybase, PostGres Databases, flat file backups, etc, and provides various other features. These status codes appear in exit status and command output for the ltid,
tpclean, tpreq, and tpunmount commands, and in system or debug logs. Programs
that call those commands, such as media and device management user interfaces
and the vmoprcmd command also presented these codes.
Below are some of the NetBackup Device management status code 21 to status code 25 which may be received while using the Symantec NetBackup tool.
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 you manually assign
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 cannot be serviced. (ltid is the Media Manager
device daemon on UNIX and Linux 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 function correctly on
¦ If ltid is not running, start ltid and try the operation again. On UNIX and
Linux, run /usr/openv/volmgr/bin/ltid, and on Windows, start the
NetBackup Device Manager service.
¦ If ltid is already running, check for the existence and permissions of the lock
file itself and the lock file directory, which are as follows:
/usr/openv/volmgr/misc/.ltipid (UNIX and Linux) or install_path\
Volmgr\misc\.ltipid (Windows). Terminate the ltid process if it is running.
Create the lock directory or folder and adjust the permissions as needed so
that ltid can obtain the lock.
¦ On UNIX and Linux, check the msgget man page and look for suggestions on
how to troubleshoot the system message queues.
Device management status code 23
Message: Invalid Drive Number
Explanation: A request was made for drive, but no such drive can be found in the
RecommendedAction: Ensure that ltid was stopped and restarted after changes
were last made to the device configuration. (ltid is the Media Manager device
daemon onUNIXand Linux or the NetBackup Device Manager service on Windows.)
Display the device configuration (by using tpconfig -d or other means) to view
the list of valid drives. Specify the drive name or index as appropriate for the
interface being used.
Device management status code 24
Message: Requested drive could not be reserved
Explanation: An attempt was made to reserve a shared drive, but the drive
reservation request failed. This status code is related to the internal
implementation of the SSO feature. It is not related to SCSI Reserve or Release.
RecommendedAction: This condition is expected for any shared drives that are
retried automatically. If problems persist, verify the following: the EMM server
services requests and it does not list drives as reserved to hosts that currently do
not use the drives.
Device management status code 25
Message: File name does not exist
Explanation: A logical tape file or help file cannot be found. The tpunmount
command was probably issued with a logical tape file specified that does not exist
for this user.
RecommendedAction: Check for existence of the logical tape file at the file path
specified. The specified file path must match the exact case-sensitive path that
was used when the tape mount was requested. Submit the request again with the
correct file path. If the condition occurs during operator display of a pending
request error message, check to see if the help files are properly installed at the
following: /usr/openv/volmgr/help/robots/robot_type/help_file name (UNIX
andLinux) or at install_path\Volmgr\Help\Robots\robot_type\help_file_name
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup Device management status code for SQL Server, Oracle, MySQL, Sybase, Postgres, etc on Windows and Linux Operating Systems.