Disaster recovery deployment

The disaster recovery (DR) deployment model uses high availability (HA) clusters distributed across separate geographic areas.

Disaster recovery (DR) is a method where the two high availability (HA) data center configurations are separated geographically. In the event of a localized disaster at the primary site, the physically removed data center on the secondary site can resume functions with minimum downtime.

If there were external systems used in the setup, it is essential to restore the network level connectivity. Some examples for these external systems include any external key vaults, Git, and so on. All the firewall rules, IP addresses added to trusted list, host-names referred in configurations are still intact and available to the restored services.

Nota: The Control Room clusters in the primary and secondary disaster recovery sites are recommended to use a minimum of three nodes each because a three-node configuration can help avoid split-brain issues with two-node clusters and increase security by using node authentication and transport layer security (TLS) features.

The following image shows the Automation Anywhere and data center cluster components for three nodes in primary and secondary sites configured for disaster recovery. The Automation Anywhere components are shown in orange and components provided by your organization are shown in blue. Components that are centrally hosted on cloud and managed by Automation Anywhere such as license server are shown in white.

Disaster recovery methods

There are two ways to perform disaster recovery - Image based replication and Warm standby. Choose the option that meets your business continuity requirements.

Automation 360

Disaster recovery deployment