Symantec NetBackup Media Manager status code 71 to status code 75

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

Media Manager status code 71
Message: failed sending to vmd
Explanation: Anattempt to write data to avmdsocket failed.vmdis the NetBackup
Volume Manager daemon (UNIX and Linux) or NetBackup Volume Manager service
(Windows).
¦ 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 system where vmd is running. The system usually is termed the
Media Manager host or EMM server and defaults to the local system in some
user interfaces (such as vmadm). Possible causes for the error are high network
load, missing operating system patches or service packs, or unexpected vmd
process failure.

Media Manager status code 72
Message: failed receiving from vmd
Explanation: An attempt to read data from a vmd socket failed. vmd is the
NetBackup Volume Manager daemon (UNIX and Linux) or NetBackup Volume
Manager service (Windows).
¦ 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 system where vmd is running. The system is usually termed the
Media Manager host or EMM server and defaults to the local system in some
user interfaces (such as vmadm). Possible causes for the error are high network
load, missing operating system patches or service packs, or unexpected vmd
process failure. Also, the socket read may have failed because the requested
operation did not complete within a specified time period. The robotic process
and vmd interactions can affect some requests to vmd; check the system log
for errors on the robotic control host.

Media Manager status code 73
Message: invalid query type
Explanation: An invalid volume query request was attempted.
¦ 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 and user interface binaries are at a compatible
version level.

Media Manager status code 74
Message: invalid number of cleanings
Explanation: Arequest was made to change the number of cleanings that remains
for one or more volumes in the volume configuration.Whenthe request was made,
the specified value was not within the acceptable range. The number of cleanings
value may also be invalid in the number of mounts or cleanings field of a bar code
rule.
¦ 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 a number of cleanings value within the acceptable range of 0 to
2,147,483,647.

Media Manager status code 75
Message: invalid change type
Explanation: An invalid volume change request was attempted.
¦ 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 and user interface binaries are at a compatible
version level.

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 *