Netbackup port range

Symantec NetBackup 7.6 Network Ports Reference Guide

http://www.symantec.com/docs/DOC6716

Netbackup uses 1556 for backup only. Some additional ports are also used, but that very much dependent on the configuration. 

Hi Nicolai , after reading this guide , I filtered the port ranges and pasted above.

I am not sure if the above mentioned ports are enough for data transfer from client to master / media server...

need your suggestion.

is this a pure VM backup configuration. Will agent based backup be used as well ?. What is the transfer method for VM backups ?

yes , all client servers are VM , Master / media servers are physical

for VM Backup -- Snapshot backup method ( SAN transport mode for SAN datastores and NDB mode for NFS datastores) and exclude DB backups.

For exchange -   exchange running on VM will be agent base backup

For SQL - SQL running on VM will be agent base backup

CIFS will be mapped to master server and get backed up via snapshot backup. 

HI SDO,  

Protocol name means transport protocol ..is it ? I have mentionedd as TCP....or something else you want to say ?

NBU version - 7.6.0.3

I will use exchange and VM GRT , please suggest the port range

Please suggest the  LU (LiveUpdate) port range  & OpsCenter 

Maybe also UDP/162 and or TCP/162 if you master, master/media, media are appliances and you want them to be able to send SNMP traps.  And again, if you have appliances, maybe also TCP/123 (for NTP time server requests).

Master Media servers are not appliance. i want to send SNMP alerts by using nebackup MIB's and ops center. any ports required for this ?

I will add these ports also as you have suggested -

UDP/53 and TCP/53 for DNS
port TCP/25 outbound from master server
TCP/22 (ssh) 
TCP/3389 (rdp) for Windows

thanks Nicolai, 

Media -> ESX TCP/902 is missing in my list ...I will add it.

My doubt is , if  4-5 policies starts running at the same time and it will backup multiple clients ( example 20 clients) , do you think these ports are enough for data transfer ?

From the port guide - page 17

TCP port 111 (portmapper) needs to be open from the client to the media server.

TCP port 7394 (nbfsd) needs to be open from the client to the media server.

Regardig OPScenter - see page 19 in the port guide.

It would be really helpfull if you had a network diagram and location of firewalls. Port opening only matter if firewalls are in place. That the "possible firewall" on the opscenter drawing page 20.

yes - you do not need to worry. It's a non-issue. 

There is a complicated technical answer behind that is out of scope right now.

thanks Nicolai, 

Noted - 

TCP port 111 (portmapper) needs to be open from the client to the media server.

TCP port 7394 (nbfsd) needs to be open from the client to the media server.

Checking page 19 for ops-center.. I will revert back in few mins