Unsolved

Closed

1 Rookie

 • 

115 Posts

638

June 14th, 2023 19:00

Networker backup and replication ports

What are the TCP/UDP ports needed for networker to do backup and replication from one site to another site?

we are setting up our DR site to host the Datadomain backup so that backup will be replicated from main DC to DR site.

June 15th, 2023 11:00

instead of the PDF, from nw19.7 onwards, there are now also online resources https://www.dell.com/support/manuals/en-uk/networker/nw_p_security_config/port-usage-and-firewall-support?guid=guid-deb317bd-da5b-4417-85a5-f26891ce8b6f&lang=en-us containing the same information and https://www.dell.com/support/manuals/en-uk/networker/nw_p_security_config/configuring-the-service-ports-on-the-firewall?guid=guid-7de91d19-2f80-4d57-bd3d-b92a9e007a29&lang=en-us from the same nw19.7 security configuration guide.

One thing that might complicate things required, is if and when you use Networker storage nodes (NW SN) to be used in the cloning of backups. If you use a NW SN on one location to perform the read and another NW SN on the target location to perform the write (even though data while performing NW CCR (clone controlled replication) would be performed between the DD systems, those two NW SN's would need to be able to communicate with each other over the whole NW Service Ports range 7937-9936. This si something that is not mentioned in the guide as it only shows ports needed between DD systems, not what to do if you have two NW SN's involved.

Peculiar thing is also that NW CCR cloning then crawls to an almost standstill, but it does not fail (alas). It is occurring with meager kb p/s instead of using the available bandwidth (which can be throttled on DD end if you are not supposed to use all bandwidth).

If however you use one NW SN (or even the backup server, which might not be preferred, if additional load is undesired), then having access to both local and remote ddboost devices would work, unlike when having a different read as the wrote NW SN, requiring both NW SN's to also be able to talk to each other as well.

1 Rookie

 • 

115 Posts

July 24th, 2023 08:00

previously we are doing cloning from DD6900-prod to DD6900-DR on the same subnet.

after moving to DR Site, DD6900-prod ------> DD6900-DR (new) with different IP address range.

the new connection is over the Internet using site-to-site IPSec VPN. is there anything we need to take note after moving to the DR site for the DD6900-DR ??

July 31st, 2023 14:00

have a look a the host entries on both DD's, so that on each the other is specified with the intended IP address to be used to replicate towards, especially if DD's have multiple interfaces to be used for different functionality as you might have a specific replication interface for example, so that it might not use the management interface for example... way back when, we had cloning between two dd's running over the 1Gb management interface in between locations instead of the intended 10Gb replication interface.

So we have stated the the name with which the DD's are defined within NW, also in the DD hosts files with that name and the shortname for the replication interface to be used of the other DD. As that gives you full control over exactly which interface will be used towards the remote DD. Do the same on the remote target DD pointing to which interface to use on the source DD.

No Events found!

Top