Symantec NetBackup Media Manager status code 81 to status code 85

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

Media Manager status code 81
Message: robot type and volume group mismatch
Explanation: A request was made to add volumes or change volume residences
in the volume configuration. The robot type and volume group that is associated
with the volume configuration changes are in conflict with the requirements for
volume groups. All volumes in a volume group are required to have the same
residence, which includes having the same robot type.Arequested operation may
have tried to associate the special No Volume Group name “—” with a robotic
residence.
¦ 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.
¦ Ensure that the specified robot residence and volume group are compatible
with other volumes in the volume configuration that are in the specified volume
group. Do not move volumes in the special No Volume Group name to a robotic
residence without moving them to a new or auto-generated volume group.
Choose a different volume group on the request, or let the volume group be
automatically selected. Volume group selection depends on the specific
interface being used.

Media Manager status code 82
Message: robot host and volume group mismatch
Explanation: A request was made to add volumes or change volume residences
in the volume configuration. The robot host and volume group that is associated
with the volume configuration changes are in conflict with the requirements for
volume groups. All volumes in a volume group are required to have the same
residence. This residence includes having the same robot host, where robot host
equivalence is defined as having the same case-sensitive robot host string.
¦ 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.
¦ Ensure that the specified robot residence and volume group are compatible
with other volumes in the volume configuration that are in the specified volume
group. Do not try to add volumes for a robot host by using a different form of
the robot host name. For example, acme is not the same as acme.symantec.com.
Use the same host name that is used for other volumes in the volume group.
If the robot host needs to be changed for volumes in a volume group, do the
following: use a single move volume group request (available only in certain
media management interfaces) to move the volume group to stand-alone
residence. Then move the volume group back to the robotic residence. Specify
the robot control host that you want to be associated with the new volume
group.

Media Manager status code 83
Message: device management error
Explanation: One of the device management errors occurs during the execution
of vmphyinv.
Recommended Action:
Examinecommandoutput, 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 84
Message: this machine is not the database host
Explanation: A request was made to initiate vmd on a host other than the local
host. vmd is the NetBackup Volume Manager daemon (UNIX and Linux) or
NetBackup Volume Manager service (Windows).
vmdport numbers other than the default or use of unsupported options can affect
the referenced host and port in the interfaces that start vmd.
¦ Initiate vmd on the local host only, by logging on to the host where vmd needs
to run Start vmd on that host. On UNIX and Linux, run
/usr/openv/volmgr/bin/vmd [-v].OnWindows, start the NetBackup Volume
Manager service in Services of the system Control Panel.
¦ If more information is needed to explain the problem, 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.
¦ Make sure port numbers are consistent.

Media Manager status code 85
Message: volume daemon fork failed
Explanation: A Media Manager daemon or service cannot create a child process
due to an error from the system. This error probably is intermittent, based on the
availability of resources on the system.
¦ Restart the service at a later time and investigate the system problems that
limit the number of processes.
¦ 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 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 *