SSO - EMM interface initialisation failed, status = 334

[Itegral]

I have NetBackup 7.1 on Windows 2008 and having an issue with my SAN media servers (SSO) i.e. facing “EMM interface initialisation failed, status = 334” error.

 Scenario is as follows; 

• The master is a media server as well (Windows 2008) has 2 NICs with IP addresses x.x.x.136 and x.x.x.26.
• x.x.x.136 is for Production and x.x.x.26 is for management network
• We want to use management network to communicate with SAN media servers and clients
• The master/media server hostname is nbu01 resolves to IP address x.x.x.136 (Production)
• The nbu01 has another alias on DNS server i.e. nbu01-man resolves to IP address x.x.x.26
• The SAN media servers were installed with Master server nbu01-man

Am I missing something above?

The EMM database seems OK on the master and the entries are correct for the media servers. The nbemmcmd -listhost command on Master show the complete list of Media servers.

But on the media server(s) it is not communicating: 

c:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listsettings -machinename cms01-man

NBEMMCMD, Version:7.0.1
Failed to initialize EMM connection.  Verify that network access to the EMM server is available and that the services nbemm and pbx_exchange are running on the EMM server. (195)

Command did not complete successfully.

[Nicolai]

You can't use a alias in Netbackup. nbu01-man need to be a A record. The media sever must be able to resolve nbu01-man both forward and reverse (master server likewise).

Please also post the full sub networks / Netmask of x.x.x.26 and x.x.x.136.

[rookie11]

use bpclntcmd command, ip to host , host to ip, option.

run this command from master to media and vice versa 

[Kevin_Good]

Symantec NetBackup Administrator's Guide for Windows Page 58
http://www.symantec.com/docs/TECH135525

REQUIRED_NETWORK
The REQUIRED_NETWORK entry specifies the required route for backup traffic in an
environment where the network traffic is segregated.
For example, an environment can contain a production network at 145.21.14.0
and a backup network at 192.132.28.0.
To indicate that NetBackup use only the backup network, use bpsetconfig to add
the following entry to the registry:
REQUIRED_NETWORK = 192.132.28.0

Note: If the variable is set and the network is not available, all connections fail
and no backups are performed.

[Kevin_Good]

You will need to stop NetBackup Services on Media Servers

Stop PBX on Media Servers

You will need to stop NetBackup Services on Master Server

Stop PBX on Master Server

Wait 3 Minutes

Start PBX on Master Server

Start NetBackup on Master

Start PBX on Media Servers

Start NetBackup on Media Servers

Test Connectivity

[Omar_Villa]

this option cannot be use for FT media servers, what u need is to add the backup name to emm as an alias with nbemmcmd. Be sure dns works fine. EMM error 195 is very similar to 196 try to follow https://www-secure.symantec.com/connect/articles/troubleshooting-emm-error-196. Please let us know Regards

[Marianne]

Hopefully x.x.x.136 and x.x.x.26 are on different subnets? Please confirm.

See this TN for NIC selection info: http://www.symantec.com/docs/TECH54733