Appendix C. Disaster Recovery architecture and components

In the diagram below, you can find the DR infrastructure components.

There are three infrastructural layers. From the bottom to the top:

  1. Physical layer: hardware nodes combined in a highly available cluster.
  2. Software-defined infrastructure layer: Acronis Cyber Infrastructure installed on the hardware nodes.
  3. Service infrastructure layer: virtual machines for each DR service component and a customer's cloud infrastructure running on top of Acronis Cyber Infrastructure.

The main components of the Disaster Recovery infrastructure are listed in the table below.

Component name Description

RunVM Agent

An agent that can have one of the following three roles:

  • RunVM Backuper – an agent role responsible for backing up cloud servers.
  • RunVM Runner – an agent role responsible for creating deltas (service files that optimize a virtual machine start from a backup, including bootability and AUR fixes).
  • RunVM Gateway/Retention/CommonAgent – an agent role that acts as a hypervisor gateway and performs backup retention tasks.

One RunVM Agent can process concurrently the following number of tasks:

  • vm-create-tasks: 5
  • vm-finalize-tasks: 100
  • vm-delete-tasks: 100
  • delta-create-tasks: 10
  • delta-delete-tasks: 100

The number of RunVM Agents must be equal to the number of nodes in the ACI cluster. Thus, for two nodes you need two RunVM Agents on the two ACI nodes.

RunVM Controller

A component responsible for attaching a backup as a disk to a virtual machine. The RunVM Controller is created per recovery server in failover mode and exists as long as the respective recovery server exists. If the recovery server is deleted, the RunVM Controller is deleted automatically.

HAProxy/Dante (SOCKS5)

These virtual machines are mainly used to eliminate the need to provide a dedicated public IP address for each client. It is recommended to have at least two proxy servers of each type for high availability.

VPN gateway

A special virtual machine providing a connection between the customer’s local network and the cloud recovery site via a secure VPN tunnel. The VPN gateway is deployed on the cloud recovery site.

VPN appliance

A special virtual machine that enables connection between the local network and the cloud site via a secure VPN tunnel. The VPN appliance is deployed on the local site.

Primary server templates

Server templates from which the primary servers are launched.

PostgreSQL RDBMS

This database is currently used only for distributed locks between agents.

Virtual router ID for Virtual Router Redundancy Protocol (VRRP)

 It is used for selecting the active instance between HAProxy instances. The parameter is needed for using the other ID if the current one is already used by any device or application in the dmzvpn network.

Tunnel-server

The dr-installer needs access to the dmz network from your local machine where it is run. The tunnel-server is a temporary auxiliary server that is used for connection to the management and dmz networks. After the deployment of proxy servers, the tunnel-server is deleted.

Core Collector

It is an auxiliary server for collecting logs and core files from RunVM Agents and RunVM Controllers to troubleshoot issues.