Symantec NetBackup Robotic error code 01 to error code 04

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 are returned if a robotic daemon/process was started from the command line and an error occurs. For example, if the administrator executes the following:

/usr/openv/volmgr/bin/tl8d

and no robots are configured, the following may be returned:

TL8: No robots are configured

These status codes are also logged to the system log. Usually, robotic daemons/processes are not started from the command line, but are started automatically, as needed, when ltid starts.

Below are some of the NetBackup Robotic error code 01 to error code 04 which may be received while using the Symantec NetBackup tool.

Robot Error status code 1
Message: You must be ROOT to start daemon
Explanation: Auser other than root started a robotic daemon. This status applies
to UNIX and Linux systems only.
Recommended Action: Log on as the root user before starting robotic daemons.
Allow robotic daemons to be started automatically as needed by ltid (the device
daemon).

Robot Error status code 2
Message: LTI Daemon may not be running
Explanation: On an attempt to start a robotic daemon or process, an attempt to
connect to the ltid message queue failed. This error indicates that ltid (the
device daemon or NetBackup Device Manager service) may not be running.
¦ Start ltid so that shared memory can be initialized, allowing the robotic
daemon/process to function.
¦ If problems persist, 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 the output of the ipcs -a command to see
what resources are currently in use.

Robot Error status code 3
Message: Error in getting shared memory
Explanation: A robotic daemon/process was unable to get a shared memory
identifier associated with a segment of shared memory that ltid maintains. (ltid
is the Media Manager device daemon on UNIX and Linux or the NetBackup Device
Manager service on Windows.)
¦ 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 the output of the ipcs -a command to see
what resources are currently in use.

Robot Error status code 4
Message: Error in attaching the shared memory
Explanation: A robotic daemon/process was unable to attach a shared memory
segment that ltid maintains. (ltid is the Media Manager device daemon on UNIX
and Linux or the NetBackup Device Manager service on Windows.)
¦ 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 the output of the ipcs -a command to see
what resources are currently in use.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup Robotic error 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 *