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 Manager security.
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.
Determine whether authorization fails on vmd. Examine the debug log files for Media Manager status code 126 occurrences ("not authorized to connect to vmd").
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:
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
/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:
On the systems that have the authentication problem, remove the remote host that is not authenticated from the methods_allow.txt file and retry the operation.
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 again.
install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers
/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers