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.

 

Leave a Reply

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