Symantec NetBackup Device management status code 01 to status code 05

SQLServerF1

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 01 to status code 05 which may be received while using the Symantec NetBackup tool.

Device management status code 1
Message: Invalid Drive Type/Density
Explanation: An invalid density was specified for the -d parameter on tpreq.
Recommended Action: Check the tpreq man page (command description) for
the list of valid densities. Submit the mount request again with a valid density.

Device management status code 2
Message: Drive is currently assigned
Explanation: Arequest was made for a specified drive, but the drive was assigned.
Recommended Action: Display drive status (by using vmoprcmd -d or other
means) to see the list of drives and their assignment status. Run the request later
or first clear the drive assignment: stop application activity on the drive, unmount
the media with tpunmount, or reset the drive. If the wrong drive was specified,
submit the request again. Specify the correct drive name or index as appropriate
for the interface being used.

Device management status code 3
Message: Error in Sending Operator Message
Explanation: An attempt was made to send an operational message to ltid on
an already existing internal message queue used for inter-process communication.
(ltid is the Media Manager device daemon on UNIX and Linux and the NetBackup
Device Manager service on Windows.) An error was encountered in the message
communications. The error probably indicates a lack of system resources for
message queues.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather output from the ipcs -a command to see
what resources are currently in use.

Device management status code 4
Message: Error in Receiving Operator Message
Explanation: An attempt was made to receive a message from ltid on an already
existing internal message queue used for inter-process communication. (ltid is
the Media Manager device daemon on UNIX and Linux and the NetBackup Device
Manager service on Windows.) An error was encountered in the message
communications. The error probably indicates a lack of system resources for
message queues.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather output from the ipcs -a command to see
what resources are currently in use. Investigate whether ltid is tied up in
communications with devices or other components.

Device management status code 5
Message: Error in Sending Daemon Message
Explanation: ltid made an attempt to send an internal process communications
message to a robotic daemon or process by using an already existing internal
message queue. (ltid is the Media Manager device daemon on UNIX and Linux
and the NetBackup Device Manager service on Windows.)Anerror was encountered
in the message communications. The error probably indicates a lack of system
resources for message queues.
¦ Examine command output, debug logs, and system logs for a more detailed
message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ On UNIX and Linux servers, gather output from the ipcs -a command to see
what resources are currently in use. Investigate whether the robotic daemon
or process on the local device host is tied up in communications with devices
or other components.

Hope this was helpful.

Thanks,
SQLServerF1 Team
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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *