API Doc
Search Docs...
⌘ K
OverviewDeploymentManagementOperationSecurityReferenceGlossary
    ABDR 2.3.0
  • Deploying Arcfra Backup & Disaster Recovery>
  • Requirements>
  • Planning the replication service

Planning networks

To ensure that the replication and recovery process runs properly, it is necessary to plan the network for the replication service before deployment. Below is a network topology diagram of the replication infrastructure.

The replication service involves three key networks: management network, storage network, and replication network. Each network serves a distinct purpose.

  • Management network: Used to manage replication resources.

  • Storage network: Used to read and write data of virtual machines during replication.

  • Replication network: Used to transfer replication and failback data to the peer replication service.

Network requirements

If the replication service is deployed in an ACOS (AVE) cluster, make sure that VM networks that meet the requirements in the table below are already configured in the cluster before deployment. If not, refer to the Creating a VM network section in ACOS Administration Guide to create networks.

Network type VM network requirements Requirements for the virtual distributed switch of the VM network
Management network The VLAN type is Access, and the replication service can connect to AOC through this VM network. Associated with at least one network port on each host in the ACOS (AVE).
Storage network The VLAN type is Access, and the replication service can connect to the storage network of the cluster to which the virtual machines to be replicated belong through this VM network.
Replication network
  • If the management network or storage network of the replication service to be deployed is connected to the peer replication service, the replication NIC can directly reuse the management NIC or storage NIC, without the need to create an additional VM network.
  • If neither the management network nor the storage network of the replication service to be deployed is connected to the peer replication service, the VLAN type must be Access, and the replication service must be able to connect to the peer replication service through this VM network.

Planning IP addresses

When deploying the replication service, at least a management IP and a storage IP need to be planned for each replication service.

Taking a single replication service as an example, you need to plan the network as shown in the following table accordingly.

Network type IP type IP address Subnet mask Gateway
Management network Management IP xx.xx.xx.xx xx.xx.xx.xx xx.xx.xx.xx
Storage network Storage IP xx.xx.xx.xx xx.xx.xx.xx -
Replication network Replication IP (optional) xx.xx.xx.xx xx.xx.xx.xx -

Note:

  • The management IP, storage IP, and replication IP of the replication service cannot be assigned to the same network segment.

  • The IP addresses cannot be the same as the IP addresses of already deployed replication services.

  • The IP addresses cannot overlap with any IP addresses within the following CIDR ranges:

    • 169.254.0.0/16
    • 240.0.0.0/4
    • 224.0.0.0/4
    • 198.18.0.0/15
    • 127.0.0.0/8
    • 0.0.0.0/8