Read and Review Automation Anywhere Documentation

Automation 360

Close Contents


Open Contents

High availability and disaster recovery deployments

  • Updated: 12/28/2022
    • Automation 360 v.x
    • Install
    • RPA Workspace
    • Overviews

High availability and disaster recovery deployments

High availability (HA) provides a failover solution if a Control Room service, server, or database fails. Disaster recovery (DR) provides a recovery solution across a geographically separated distance in the event of a disaster that causes an entire data center to fail.


The Automation Anywhere implementation of high availability and disaster recovery reduces downtime and maintains continuity of business (CoB) for your automation and bot deployment activities.

High availability
Refers to a system or component that is continuously operational for a desirably long period.
Disaster recovery
Involves a set of policies and procedures to enable the recovery or continuation of vital infrastructure and systems following a natural or human-induced disaster.

The Automation Anywhere components and configuration leverage your existing HA and DR infrastructure, load balancing, and failover systems to protect your bots and related data. Contact your data center administrator for your approved local HA and DR procedures.

Required HA and DR infrastructure components

Distributed approach
The Control Room provides the flexibility to process a large number of requests. Deploy multiple instances of Control Room on multiple physical or virtual servers as required.

Automation 360 On-Premises prerequisites

Load balancing
Performed by a load balancer, this is the process of distributing application or network traffic across multiple servers to protect service activities, allowing workloads to be distributed among multiple servers. This ensures bot activity continues on clustered servers.

Load balancer requirements

Databases use their own built-in failover to protect the data. This ensures database data recovery.

Configure synchronous replication between the primary (active) and secondary (passive) clustered Microsoft SQL servers in the data center. This ensures consistency in the event of a database node failure.

For synchronous replication, configure the database using publisher and subscriber model in Microsoft SQL Server from the primary disaster recovery site to the secondary disaster recovery site that is at a geographically separated location from the primary site.

Replicate data between primary and secondary sites

As synchronous data replication is configured between multiple Control Room servers, license information that is centrally stored in the database or license cloud, is shared within HA clusters and across DR sites.

Licenses and cloud services

Send Feedback