Overview:
Before the upgrade, the media server had been configured to use vnetd communications with the master server (See Related Documents for details) and the required ports (the bpcd port 13782 and the vnetd port 13724) were open both ways within the firewall.

After upgrading a NetBackup 5.x media server (separated from the master by a firewall) to NetBackup version 6.x, the nbpushdata -add command failed with error "EMM Initialization failed, status = 195".

Note: After upgrading a NetBackup 5.x media server to NetBackup 6.x the nbpushdata -add command moves data from the NetBackup 5.x database files (a subset of the NetBackup catalog) into a newly created EMM database. For this process to work, the new NetBackup 6.x processes (including the Private Branch Exchange process) must be running on the master server and its associated media servers before you upgrade and run the nbpushdata -add command.  This is true no matter where you are running the command -- including on the far side of a firewall.

The EMM database creation process establishes that the EMM server can communicate with any additional servers in your configuration, and it does not include servers in the database if it cannot establish a connection and determine that NetBackup processes are running on the server.

Cause:
NetBackup 6.0 and later require Private Branch Exchange (PBX) to operate. NetBackup versions earlier than 6.0 did not require PBX. However, there may be other Veritas or Symantec products installed in the current NetBackup 5.x environment that require this software.  Regardless of whether PBX already exists in the current NetBackup 5.x environment, the upgrade to NetBackup 6.5 installs or upgrades PBX automatically.

All communications between all media servers and the EMM database are performed by the PBX components installed on all NetBackup 6.x master and media servers.

For successful communications between a media server and a master server separated by a firewall, in addition to the bpcd port (13782) and the vnetd port (13724); the new PBX dedicated port (1556) must be open both ways (from the master to the media server and vice versa) in the firewall.

If the PBX dedicated port (1556) is not open both ways in the firewall, the nbpushdata -add command (which uses the PBX components to update the EMM database) will fail with media manager status code 195 as seen above.

Solution:
The following destination ports should be opened on the firewall:

master >> media

media >> master

media >> media *

* If the media server is in a Shared Storage Option (SSO) environment, then port 13701 (vmd) will need to be opened between all media servers sharing a particular set of drives.

More information on port usage by NetBackup processes can be found in the NetBackup 6.0 Port Usage Guide, linked below.