Symantec NetBackup Media Manager status code 121 to status code 126

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

Media Manager status code 121
Message: failed appending to rule database
Explanation: A request was made to add, change, or delete a bar code rule. A bar
code rule record cannot be appended to the bar code rule database file.
Recommended Action:
Examine the daemon debug log for a more detailed message on the system error.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.

Media Manager status code 122
Message: barcode tag is not unique in rule database
Explanation: A request was made to add a bar code rule. The specified bar code
tag was a duplicate of the tag for an existing bar code rule.
Recommended Action: On the add bar code rule request, specify a bar code tag
that is not already in use.

Media Manager status code 126
Message: not authorized to connect to vmd
Explanation: A caller requesting services from vmd is either not authenticated
or not authorized. Or a problem is encountered when two systems attempt to
authenticate one another.
¦ See the NetBackup Security and Encryption Guide for information on vmd
security.
vmd security is based on NetBackup authentication or authorization, but has
extensions for handling SERVER entries in the Media Manager configuration
file.
¦ Examine the debug log files for a more detailed message on the authentication
or the authorization problem.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Correct the vmd security configuration by adjusting the authentication
configuration, the AUTHORIZATION_REQUIRED entry, and SERVER entries.
¦ If an authentication problem (rather than a configuration issue) is suspected,
do the following:
¦ Ensure that the authentication libraries exist:
Windows:
install_path\NetBackup\lib\libvopie.dll
install_path\NetBackup\lib\libvnoauth.dll
UNIX and Linux (except HP-UX):
/usr/openv/lib/libvopie.so
/usr/openv/lib/libvnoauth.so
UNIX and Linux (HP-UX only):
/usr/openv/lib/libvopie.sl
/usr/openv/lib/libvnoauth.sl
¦ Check the methods_allow.txt files on the systems that have problems to
ensure that authentication is enabled. The files are in the following
locations:
Windows: install_path\NetBackup\var\auth
UNIX and Linux: /usr/openv/var/auth
¦ On the systems that have the authentication problem, remove the remote
host that is not authenticated from the methods_allow.txt file.
For example, if Host A and Host B have the problem, remove Host A from
the file on Host B, and vice versa.
Retry the operation.
If the problem still exists, the connection problems are not related to
authentication.
If connections are successful, proceed to the next step.
Run bpauthsync -vopie on the master server to synchronize the key files
on the systems again.
On Windows:
install_path\NetBackup\bin\admincmd\bpauthsync -vopie
-servers
On UNIX and Linux:
/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers
¦ Add back the removed hosts and retry the operation.

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 *