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.
Recommended Action:
Examine the command output (if available) and the daemon and reqlib debug logs for a more detailed message on the error.
See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference 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 NetBackup Logging Reference Guide.
If necessary, start the robotic process.
Ensure that only one configured robot control host exists for each TLD 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 the requests when connections to it are attempted.