Symantec NetBackup Media Manager status code 41 to status code 45

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. Media Manager software is part of NetBackup which manages the storage devices and removable media.

Below are some of the NetBackup Media Manager status code 41 to status code 45 which may be received while using the Symantec NetBackup tool.

Media Manager status code 41
Message: invalid media ID for naming mode
Explanation: Arequest to add multiple volumes with a first media ID and a media
ID style failed. It fails because the media ID specified was not compatible with the
media ID naming style provided.
Recommended Action: Provide a first media ID that fits the selected style. For
example, the media ID style is two characters and four digits. Then the least
significant four characters in the first media ID must be digits in the range 0 to
9. Alternatively, select a media ID style that fits the specified first media ID.

Media Manager status code 42
Message: cannot connect to robotic software daemon
Explanation: A connection to a robotic software daemon or process cannot be
established. This error can occur when a process tries to connect to the robotic
process that is not running. It can also occur if the network or server is heavily
loaded and has slow response time.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Identify the robotic process: look at the robot type and at the robot host on
the robotic request or the robot host field of the volume being operated on.
¦ Verify that the robotic process to use for robotic control is available
See “Media and device management components” in the Troubleshooting
Guide.
If necessary, start the robotic process.
¦ Ensure that only one configured robot control host exists for each TL8, TLD,
and TLH robot. Also ensure that all volumes in the volume configuration have
a robot host that matches the configured robot control host.
¦ Change the volumes or reconfigure the robot in the device configuration as
needed.
¦ Check the system log on the robot control host to see if the robotic process
processes requests when connections to it are attempted.

Media Manager status code 43
Message: failed sending to robotic software daemon
Explanation: An attempt to write data to a robotic software daemon or process
socket failed.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Identify the robotic process: look at the robot type and at the robot host on
the robotic request or the robot host field of the volume being operated on.
Verify that the robotic process to use for robotic control is available and that
it handles requests.
¦ Identify the robot control host by checking the device configuration. Only one
configured robot control host should exist for each TL8, TLD, and TLH robot.
All volumes in the volume configuration should have a robot host that matches
the configured robot control host.
¦ Check the system log on the robot control host to see if the robotic process
processes requests when communications with it are attempted.

Media Manager status code 44
Message: failed receiving from robotic software daemon
Explanation: An attempt to read data from a robotic software daemon or process
socket failed.
¦ Examine command output (if available) and the daemon and reqlib debug
logs for a more detailed message on the error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Identify the targeted robotic process: look at the robot type and at the robot
host on the robotic request or the robot host field of the volume being operated
on. Verify that the robotic process to use for robotic control is available and
that it handles requests.
See “Media and device management components” in the Troubleshooting Guide.
¦ Identify the robot control host by checking the device configuration. Only one
configured robot control host should exist for each TL8, TLD, and TLH robot.
All volumes in the volume configuration should have a robot host that matches
the configured robot control host.
¦ Check the system log on the robot control host to see if the robotic process
handles requests when communications with it are attempted.
See “Resolving network communication problems with UNIX clients” in the
Troubleshooting Guide.
See “Resolving network communication problems with PC clients” in the
Troubleshooting Guide.

Media Manager status code 45
Message: failed changing terminal characteristics
Explanation: When an attempt was made to change the mode for terminal input
between cooked and raw, a system call failed.
Recommended Action: Examine the user interface output for the system error
that is associated with the failed system call. Then troubleshoot according to
operating system vendor recommendations.

Hope this was helpful.

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