Ports required for recovery of assets using NetBackup
Following is the list of the ports required for Resiliency Manager for recovery of assets using NetBackup:
Table: 1. Ports for RM for NetBackup communication
Ports used | Purpose | For communication between | Direction | Protocol |
|---|---|---|---|---|
1556 | Used for establishing websocket channel if NetBackup primary server is reachable from RM | RM and NetBackup primary server | Out-bound on RM | Proprietary |
14176 | Used for all websocket communication | RM and NetBackup primary server | In-bound on RM | Proprietary |
Following is the list of ports required for IMS for recovery of assets using NetBackup:
Table: 2. Ports for IMS for NetBackup communication
Ports used | Purpose | For communication between | Direction | Protocol |
|---|---|---|---|---|
1556 | Used for NetBackup discovery | IMS and NetBackup primary server | Out-bound | Proprietary |
Following is the list of ports required for NetBackup primary server for recovery of assets using NetBackup:
Table: 3. Ports for NetBackup primary server for Resiliency Platform communication
Ports used | Purpose | For communication between | Direction | Protocol |
|---|---|---|---|---|
1556 | Used for establishing websocket channel if NetBackup primary server is reachable from RM | RM to NetBackup primary server | In-bound on NetBackup primary server | Proprietary |
14176 | Used for discovery and operations | RM and NetBackup primary server | Out-bound on NetBackup primary server | Proprietary |
If NetBackup web service is configured on a different port than 1556, you have to open that port instead of 1556 in above tables. For port table 1 and 3, the firewall should open port for local data center and remote data center across site.
For example, RM should be able to communicate with NetBackup primary server in DR and vice versa to ensure that any DR activity can be performed seamlessly.
In addition to the ports listed above, you need the following ports open: