On Media Server "nbemmcmd -getemmserver" command showed error "Failed to initialize EMM connection. Verify that network access to the EMM server is available and x_exchange are running on the EMM server (195)".
In Media Server's event viewer I found error "EMM interface initialization failed, status = 334".
Verification
Ran "nbdb_ping" on Master Server:
Database [NBDB] is alive and well on server [NB_masterserver]
Ran "nbemmcmd -getemmserver" on Master Server:
Ran "nbemmcmd -getemmserver" on Media Server:
Failed to initialize EMM connection. Verify that network access to the EMM server is available and x_exchange are running on the EMM server. (195)
Command did not complete successfully.
OBBC Verification
According to the article if ODBC driver doesn't have Version, company, etc updated then error 334 may show up.
My ODBC
The path to a critical DLL for allowing ODBC communication to the EMM database must be found at the specified location. The DLL is called DBODBC11.DLL. I checked and confirmed that the DLL existed in the correct location, \<InstallPath>\VERITAS\NetBackupDB\WIN32\DBODBC11.DLL. Since DLL was there, I checked the registry to make sure it is pointing to the correct working path for this DLL:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\NB SQL Anywhere\ and verified the keys named Driver and Setup are pointing to the correct path.
Regedit verification:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\NBAZDB\
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\NB SQL Anywhere\
Driver & Setup keys were setup correctly.
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers\
However, in ODBC Drivers there was no key named "NB SQL Anywhere", instead there was "NB Adaptive Server Anywhere 9.0.2"
Then I opened
C:\Program Files\VERITAS\NetBackupDB\data\ vxdbms.conf file in notepad
VXDBMS_NB_DATABASE = NBDB (Correct)
VXDBMS_AZ_DATABASE = NBAZDB (Correct)
VXDBMS_ODBC_DRIVER = NB SQL Anywhere (Incorrect)
Changes:
I renamed "NB SQL Anywhere" to "NB Adaptive Server Anywhere 9.0.2" in Regedit and updated vxdbms.conf with VXDBMS_ODBC_DRIVER = NB Adaptive Server Anywhere 9.0.2
ODBC Drivers entry got updated.
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config
"Server" string value did not have Media Server's name listed so I updated it. (Each Server name must be separated by a line break (one server name per line). Spaces are not allowed.)
I just realized that I did not have EMM Port number 1556 enabled in the Group Policy for Firewall, so I got it enabled as well.
Rebooted the Master and Media Servers.
I was able to map the Media Server's VTL to my Master Server.