How to Create a Plan for Replication Across Sites

The replication across site feature allows you to use the same Console to replicate data between different sites. The following diagram illustrates the connection among Console, Site 1 and Site 2:

Console (For example, in public network), Site 1 (For example, in a private network) and Site 2 (For example, in another private network) can be in different network segments. Site 1 and Site 2 are managed by console through the gateway.

The diagram gives an example to illustrate this feature of UDP, which is just a reference because the real environment that you are using may not be similar to the one described here. The example aims to replicate data from Site 1 source RPS to Site 2 destination RPS. Gateway in Site 1 and Site 2 can connect to the Console through the proxy or NAT. The proxy and NAT should be properly configured.

Description of diagram:

• Proxy1 or NAT1 has both public interface and private interface. For example: IP-1 as public IP is in the same segment with console and IP-2 as private IP is in the same segment with Site1. In the network setting of Gateway1 machine, default gateway is set to private IP of Proxy1 or NAT1.
• Proxy2 and NAT2 also have the same setting with Proxy1/NAT1, besides that NAT2 needs extra configuration of a port redirection rule so that from the public network one can access the private service by this mapping. In this example, that is the source RPS through which NAT2 port redirection can connect to destination RPS.
• With windows server 2012R2 OS, both windows GUI and command could set port direction for NAT. Here is an example command, which means: input this address from source RPS web explorer https or http://<NAT2 IP-1>:<port number=8855>, and it will redirect to destination RPS https or http://<destination RPS IP=192.168.30.102>:8014, then you can execute the replication cross site.

• netsh interface portproxy add v4tov4 listenport=8855 connectaddress="192.168.30.102" connectport=8014 protocol=tcp