Symantec NetBackup Media Manager status code 76 to status code 80

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

Media Manager status code 76
Message: cannot get host name
Explanation: The system call gethostname(3C) failed during an attempt to obtain
the name of the local host.
¦ 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.
¦ Obtain the specific system call failure from the debug log, and investigate the
operating system functionality that is related to the failure. Run the hostname
system command to see if the command operates correctly.

Media Manager status code 78
Message: barcode does not exist in database
Explanation: A query volume by bar code request did not return a volume entry
having the specified bar code, or bar code and media type.
¦ Examine 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.
¦ Ensure that volumes are properly configured in the EMM database. Use
tpconfig -d to list the configured EMM server. Select the current server (the
one being administered) to be the same as the host, which is the correct EMM
server. Do the following so that the volume query can find a matching volume:
update the volume or the device configurations, modify volume properties, or
adjust search criteria as needed. For media in their correct slot locations, run
the Rescan or the update bar code request so the following occurs: the bar code
field in the volume configuration matches the actual bar code as interpreted
by the robotic library bar code reader.

Media Manager status code 79
Message: specified robot is unknown to vmd
Explanation: A request was made to query volumes by residence. No volumes
were found in the targeted volume configuration that matched the provided robot
number, robot type, and robot host.
¦ 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 volumes are properly configured in the EMM database. Use
tpconfig -d to list the configured EMM server. Select the current server (the
one being administered) to be the same as the host which is the correct EMM
server. Perform the following so the volume residence query can find a
matching volume: update the volume or the device configurations, modify
volume properties, or adjust search criteria as needed.

Media Manager status code 80
Message: cannot update database due to existing errors
vmphyinv is unable to update the EMM database because of the existing errors.
The errors can be as follows:
¦ A Media Manager volume record belongs to a different robot with the same
media ID as the media ID that the tape header read.
¦ The media type or media GUID or the volume pool of an assigned volume
record needs to be changed.
¦ A bar code conflict is detected and vmphyinv needs to change the bar code of
the existing volume record.
Recommended Action: vmphyinv, in such a scenario, generates a list of errors.
Examine the output. You must resolve all these errors before you run the utility
again.

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 *