The command nbemmcmd on new media server produces the error: "Failed to initialize EMM connection"

Overview :
The command nbemmcmd on new media server produces the error: "Failed to initialize EMM connection"
Note: By default, the master server and Enterprise Media Manager (EMM) server roles are installed together to the same host.  It is possible to custom configure the NetBackup domain to have the EMM server and master server roles on separate physical machines.

Cause :
Two causes have been noted:

1.The new media server hostname that is not listed as a valid server will not be allowed to connect into EMM service.  Each media server hostname must be properly added to the server list of the EMM server and master server.
 

Windows Master:

The Registry DWORD for "Server" under [HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config], did not have correct syntax for valid server listing.  Each Server name must be separated by a line break (one server name per line).  Spaces are not allowed.

 

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes
 

UNIX/Linux:

The file /usr/openv/netbackup/bp.conf file must have a valid "SERVER = <mediaserver>" line for each media server hostname.
 

2. The new media server hostname is not yet added to EMM Database on the EMM server.  Running " nbemmcmd -listhost " does not show the new media server hostname.  The command is located in the default path /usr/openv/netbackup/bin/admincmd/ for UNIX/Linux, or C:\program files\veritas\netbackup\bin\admincmd\ for Windows.

Solution:
Note: When adding hostnames, be careful of typos and conventions such as using fully qualified domain name (FQDN) and short hostname.

If the cause is because the new media server hostname is not on the EMM and master server's server list, add the hostname of the new media server into both the EMM server and master server's list.

If the cause is because the new media server is not listed as a media server type in the EMM host list, add the new media server via the nbemmcmd command.  (Run " nbemmcmd -addhost -help " for more help.)
 

HINT: The minimal switches to add to the EMM host list are as follows:
 

-addhost

-machinename <hostname>

-machinetype media

-masterserver <masterserver_hostname_as_appear_in_emm_list>

-netbackupversion <6.00_or_6.5.0>

-operatingsystem <os_type_see_list_from_help>
 

Example: nbemmcmd -addhost -machinename newhost -machinetype media -masterserver master -netbackupversion 6.50 -operatingsystem windows