Introduction

You can add DR links to connect all sites. You can configure the transfer rate, DR transmission interfaces, transmission encryption, and link alerts for DR links.

Precautions

1. Make sure that the time of the primary and secondary sites is synced with SCP. It is recommended to deploy an NTP server.

2. Data transmission for DR occupies large amounts of bandwidth, which requires dedicated DR transmission interfaces. It is not recommended to use DR transmission interfaces for management interface and VM network interface multiplexing.

Prerequisites

The primary and secondary sites for DR are added to a resource pool, and DR sites are added.

Procedure

1. Go to Resources > Disaster Recovery > Disaster Recovery > Link Management and click New Link.

2. Add links:

①When the DR link is multiplexed, you can set Max Transfer Rate to Maximum and enter a value in case that excessive bandwidth is occupied by other businesses, affecting backup data transmission between the primary and secondary sites.

②If the primary and secondary sites are deployed in the same network segment, select Layer 2 Link. If not, select Layer 3 Link.

③Select DR transmission interfaces for the primary and secondary sites. DR data is transmitted between the cluster controller servers of the primary and secondary sites.

④Click Advanced to configure the DR transmission interface of each node in the cluster.

3. Click Advanced and configure DR transmission interfaces. A DR transmission interface is an interface used to transmit backup data when the node of the interface functions as the cluster controller.

4. DR proxy interfaces are interfaces used by other nodes in the cluster to transmit DR data to the cluster controller node. Site IP addresses and DR transmission interfaces are used to transmit DR data between the primary and secondary HCI clusters, while DR proxy interfaces are used to sync data between nodes in each cluster. After a node transmits data to the cluster controller node through the DR proxy (rsync runs on each node), the cluster controller node transmits the data to the secondary HCI cluster through squid, which is deployed only on the cluster controller node. For example, an HCI cluster contains three nodes. Node 1 is the cluster controller. If Node 2 needs to sync backup data, it transmits the data to Node 1 through the DR proxy. Then, Node 1 transmits the data from the DR transmission interface to the IP address of the secondary site.