Symantec NetBackup Media Manager status code 176 to status code 181
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 176 to status code 181 which may be received while using the Symantec NetBackup tool.
Media Manager status code 176
Message: unable to find any records in the device test database
Explanation: The state file exists, but it is empty. This error indicates that no
previous test runs have occurred.
Recommended Action: None required.
Media Manager status code 177
Message: request can only be performed on the Media and Device Management
Explanation: The host this request was performed on is blocked from being a
database host. An administrator blocked the host to restrict which hosts are
allowed to be EMM servers.
¦ Verify that you specified the correct EMM server (the -h option on the
command line). If you did not specify the database host, the command line
defaults to the local host, while the console uses the currently administered
¦ Contact the administrator in charge of this configuration and verify that the
host was intentionally blocked from being a database host. If not, remove the
NOT_DATABASE_HOST flag in the host’s vm.conf file. To do so without having
to stop and restart the daemons, use:
vmquery -h <hoostname> -remove_not_db_host.
To add this entry to a host without having to stop and restart the daemons,
use: vmquery -h <hostname> -add_not_db_host.
Media Manager status code 181
Message: not authorized to connect to robotic daemon
Explanation: A caller requesting services from a robotic daemon is not
authenticated or authorized. Or when two systems try to authenticate one another,
a problem occurs.
¦ See the NetBackup Security and Encryption Guide for information on Media
Media Manager security is based on NetBackup authentication and
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
and authorization problem.
See “Setting debug logging to a higher level” in the Troubleshooting Guide.
¦ Determine whether authorization fails on vmd. Examine the debug log files for
Media Manager status code 126 occurrences (not authorized to connect to
¦ Correct the Media Manager security configuration by adjusting the
authentication configuration, the AUTHORIZATION_REQUIRED entry, the
ENABLE_ROBOT_AUTH entry, and the SERVER entries.
¦ If an authentication problem (rather than a configuration issue) is suspected,
do the following:
¦ Ensure that the authentication libraries exist:
UNIX and Linux (except HP-UX):
UNIX and Linux (HP-UX only):
¦ Check the methods_allow.txt files on the systems that have problems to
ensure that authentication is enabled. The files are in the following
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 and retry
For example, if Host A and Host B have the problem, remove Host A from
the file on Host B, and vice versa.
If the problem still exists, the error is caused by connection problems not
related to authentication.
If connections are successful after you remove the host, run bpauthsync
-vopie on the master server to synchronize the key files on the systems
install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers
On UNIX and Linux:
/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers
Add the removed names and retry the operation.
Hope this was helpful.
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.