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 status code 126 to status code 130

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 and provides various features.

Below are some of the NetBackup status error codes from Status Code 126 to Status Code 130 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 126
Message: NB database backup header is too large, too many paths specified
Explanation: Too many paths were specified in the NetBackup catalog backup
configuration to fit in a fixed-size media header. This error should not occur under
normal circumstances.
Recommended Action: Delete some of the paths from the catalog backup
configuration.

NetBackup status code: 127
Message: specified media or path does not contain a valid NB database backup
header
Explanation: The bprecover command was issued and the media ID specified
does not have valid catalog backup data.
Recommended Action: Validate that the correct media ID is used.

NetBackup status code: 128
Message: NB database recovery failed, a process has encountered an exceptional
condition
Explanation: In the catalogs that were specified for recovery, one or more cannot
be restored. For more detail, refer to the error message that precedes this status
code in the output from the bprecover command.
Recommended Action: Do the following, as appropriate:
¦ Fix the problem that was reported in the error message in the bprecover
output.
¦ Identify which NetBackup services to shut down before a NetBackup database
recovery attempt:
See “About recovering the NetBackup catalog” in the Troubleshooting Guide.
The NetBackup services should be shut down except for the NetBackup Client
Service, which must be running for the database recovery to succeed.
¦ Check the NetBackup Problems report for additional information about the
error.
The following are some possible causes:
¦ A disk may be full.
¦ The NetBackup catalog tape may be corrupt.

NetBackup status code: 129
Message: Disk storage unit is full
Explanation: As NetBackup writes to the file system for the disk storage unit,
runs out of space. Until more file system space is available, images of similar size
or larger may fail with this error when written to this disk storage unit.
In a scheduled backup job that writes to a storage unit group (which contains this
disk storage unit), the following occurs: the NetBackup scheduler requests the
storage unit with the greatest available capacity when the job is retried.
For the retry, when the scheduler requests the storage unit with the greatest
available capacity, note the following:
¦ A tape storage unit in the storage unit group has preference over any disk
storage units since tape storage units usually have more capacity.
¦ If the storage unit with the most unused capacity is busy, NetBackup skips it.
NetBackup then selects an available storage unit with the next largest, unused
capacity.
¦ If the storage unit with the greatest unused capacity is the one that lacked
capacity when the job first failed, the scheduler tries it again. That storage
unit may have more unused capacity now than it did when the job failed.
Recommended Action: Do the following, as appropriate:
¦ Either free sufficient space or add more space to the file system for this storage
unit.
¦ Lower the high capacity mark for this disk storage unit. Configure the policies
to access it through a storage unit group that provides alternative storage to
use when this storage unit fills up. Ideally, if an image exceeds the file system’s
high capacity mark, it also completes successfully. This image leaves the
storage unit in a full state (over the high capacity mark). The storage unit then
is not assigned to other jobs until its capacity falls under its high capacity
mark.
¦ If the Staging attribute is set on the disk storage unit that did not have enough
capacity, it may be unable to create free space. It cannot create space because
the backups that are staged to the disk are not relocated (eligible to be deleted
from the staging storage unit). Ensure that staging’s relocation (duplication)
jobs successfully copy enough images to provide sufficient free space for new
backups.

NetBackup status code: 130
Message: system error occurred
Explanation: An error occurred that prevents the product from operating in a
consistent fashion. This error is usually related to a system call.
Recommended Action: Do the following, as appropriate:
¦ Check the NetBackup Problems report for additional information about the
error.
¦ Check the system log for reported problems.
¦ For detailed troubleshooting information, create bpdbm, bptm, and bprd debug
log directories on the master server. Increase the unified logging level by using
the vxlogcfg command.
See “About unified logging” in the Troubleshooting Guide.
¦ Retry the operation and check the resulting debug logs.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.