Symantec NetBackup Robotic error code 14 to error code 17

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 14 to error code 17 which may be received while using the Symantec NetBackup tool.

Robot Error status code 14
Message: You must be administrator to execute
Explanation: A robotic process was started under a user account that lacks
Administrator privileges (applies to Windows systems only).
Recommended Action: Allow robotic daemons to be started automatically as
needed by the NetBackup Device Manager service. Ensure that this service starts
from a user account with administrator privilege.

Robot Error status code 16
Message: Devices located in multiple domains
Explanation: A robotic daemon or process encountered an invalid device
configuration. In this configuration, a single logical robot controls drives from
different domains.
Recommended Action: Display the device configuration using tpconfig -d or
a device configuration interface to see the robotic and the drive information that
is already configured. Ensure that the drive addresses do not span physical
domains. Drives can only be configured in the same robot if they can be used with
media from a single domain. The domain must include a single physical library
or multiple libraries that are connected by a cartridge exchange or pass-through
mechanism.

Robot Error status code 17
Message: Robotic daemon not licensed
Explanation: A robotic daemon or process was started without the required,
current product license, or a required database file was missing or corrupt.
¦ Check product documentation for supported device configurations.
¦ Obtain an additional software license that allows robots of the associated robot
type to be configured. Or, limit the configuration to robot types that current
licensing allows. Check for the existence and permissions of the
external_robotics.txt file in the /usr/openv/share directory (UNIX and
Linux) or in the install_path\NetBackup\share folder (Windows).

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.

 

Symantec NetBackup Robotic error code 09 to error code 13

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 09 to error code 13 which may be received while using the Symantec NetBackup tool.

Robot Error status code 9
Message: Error in SEMAPHORE operation
Explanation: A process was unable to perform a semaphore operation (such as
lock or unlock) associated with resources maintained by ltid. (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 10
Message: Fork failure occurred
Explanation: A robotic daemon or process could not create a child process due
to a system error. This error is probably intermittent, based on the availability of
resources on the system (applies to UNIX and Linux servers only).
¦ Restart the device daemon at a later time and investigate system problems
that limit the number of processes.
¦ Examine the system logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Restart the device daemon, then retry the operation and examine the system
log file.

Robot Error status code 11
Message: System error occurred
Explanation: A robotic daemon/process encountered a system error.
Recommended Action: 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.

Robot Error status code 12
Message: Usage error in creating child process
Explanation: A robotic daemon/process could not create a child process due to
an incompatibility between robotic software components.
¦ 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.
¦ Verify that all Media Manager binaries are at a compatible version level.

Robot Error status code 13
Message: EMM error
Explanation: The robotic daemon had a problem communicating with EMM.
¦ Make sure nbemm is running and responding to requests.
¦ 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.

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.

 

Symantec NetBackup Robotic error code 05 to error code 08

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

Robot Error status code 5
Message: Error in getting process Id
Explanation: A robotic daemon/process was unable to obtain its own process
identifier due to a system call failure.
Recommended Action: Investigate operating system functionality regarding a
process obtaining its own process identifier.

Robot Error status code 6
Message: No devices are configured on the robot
Explanation: Arobotic daemon/process was started, but no drives are configured
for the robot.
RecommendedAction: Some robotic daemons or processes do not run if no drives
are configured for them to manage. Add or reconfigure one or more drives to be
in the associated robot. Then, stop and restart ltid (the Media Manager device
daemon on UNIX and Linux or NetBackup Device Manager service on Windows).

Robot Error status code 7
Message: No robots are configured
Explanation: A robotic daemon/process was started, but no robots of the
associated robot type are configured.
RecommendedAction: Robotic daemons or processes do not run if no robots are
configured for the associated robot type. Add or reconfigure robots, then stop and
restart ltid (the Media Manager device daemon on UNIX and Linux or NetBackup
Device Manager service on Windows).

Robot Error status code 8
Message: No memory available
Explanation: A robotic daemon/process was unable to allocate memory. This
error occurs when insufficient system memory is available. This error could result
from the system being overloaded with too many processes and from insufficient
physical and virtual memory.
RecommendedAction: Free up memory by terminating unneeded processes. Add
more swap space or physical memory.

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.

 

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.