Symantec NetBackup Media Manager status code 61 to status code 65

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 61 to status code 65 which may be received while using the Symantec NetBackup tool.

Media Manager status code 61
Message: robot number and robot host mismatch
Explanation: A request is made to add or change volumes in the volume
configuration, or to issue a robot inventory update request. A specified robot host
differs from the robot host for other volumes in the same robot (defined as those
volumes having the same robot number). All volumes in the EMM database that
have a given robot number (for instance, 0) must have the same robot host name.
¦ 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.
¦ Specify the robot host in the device configuration to be the same case-sensitive
host name on all hosts where the robot is configured. Re-issue the request. As
an alternative, use move-by-volume group to move all volumes logically from
a robotic volume group to stand-alone and then back into the robot. Specify
the robot host as the host name that is used in the robot configuration. Then
re-issue the request.

Media Manager status code 62
Message: failed redirecting input to pipe
Explanation: A system pipe cannot be created.
Recommended Action: Check the interface output for the specific system error
and investigate the operating system functionality that is related to the failure.

Media Manager status code 63
Message: child process killed by signal
Explanation: An unexpected signal terminated a robot inventory update process.
¦ Examine interface output and debug logs for a more detailed message error.
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.

Media Manager status code 64
Message: no child process to wait for
Explanation: Amedia management interface attempted to wait for a child process
to complete, but unexpectedly found that no such child process existed.
¦ Examine interface output and debug logs for a more detailed message error.
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.
¦ Retry the operation (or try to use a different media management interface)
and examine the logs.

Media Manager status code 65
Message: volume group does not exist
Explanation: During a request process, a volume group cannot be found within
the existing volume entries in the EMM database.
¦ Examine interface output and debug logs for a more detailed message error.
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.
¦ Check for data integrity or consistency problems in theEMMdatabase by using
a media management interface. Delete or move volume entries so that the
volume group issues are corrected.

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 *