High Availability (HA) provides a failover solution in the event 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.
Automation Anywhere HA and DR solution
In the context of Automation Anywhere, implementation of High Availability (HA) and Disaster Recovery (DR) reduces downtime and maintains continuity of business (CoB) for your bot activities.
- High Availability (HA)—refers to a system or component that is continuously operational for a desirably long period.
- Disaster Recovery (DR)—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.
HA and DR are required for production deployments of Automation Anywhere.
Automation Anywhere leverages your existing HA and DR infrastructure. We do not provide an internal HA or DR solution. Rather 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. See your data center administrator for your approved local HA and DR procedures.
Required HA and DR infrastructure elements
- Distributed Approach—in addition to clustering Automation Anywhere and related data center components, we also recommend that you deploy the Control Room and the Enterprise Clients on separate machines.
Control Room is flexible enough to process a large number of requests. Deploy multiple instances of either Control Room or Enterprise Client on multiple physical or virtual servers, as needed.
-
Load balancing—Performed by a load balancer, this is the process of distributing application or network traffic across multiple servers to protect service activities and allows workloads to be distributed among multiple servers. This ensures bot activity continues on clustered servers.
For load balancer configuration details, see Enterprise 11: Load balancer requirements.
-
Databases—Databases use their own built-in failover to protect the data. This ensures database data recovery.
-
Between the HA clusters, configure synchronous replication between the primary (active) and secondary (passive/standby) clustered MS SQL servers in the data center. This ensures consistency in the event of a database node failure.
For the required HA synchronous replication, configure one of the following:
- Backup replica to Synchronous-Commit mode of SQL Server Always On availability groups
- SQL to Server Database Mirroring
- Between the DR sites, configure your database to provide asynchronous replication from the primary (production) DR site to the secondary (recovery) DR site that is at a geographically separated location from the primary DR site.
Sample scenario
Point all Control Room instances within the same cluster to the same database and repository files. This is required to enable sharing data across multiple servers and ensuring data integrity is maintained across Enterprise Clients accessing Control Rooms within a cluster.
HA and DR deployment models
To ensure your Automation Anywhere is protected by HA or DR, configure your data centers according to the deployment models described in:
FAQs
Fundamentally, High Availability and Disaster Recovery are aimed at the same problem: keeping systems up and running in an operational state, with the main difference being that HA is intended to handle problems while a system is running while DR is intended to handle problems after a system fails.
What is an overview of high availability and disaster recovery solutions available for SQL Server? ›
You can achieve high availability by deploying SQL Server across two Availability Zones in one Region. You can achieve disaster recovery by extending availability groups across Regions. The following diagram shows an example architecture for a solution based on Always On availability groups.
How do you achieve disaster recovery and high availability? ›
Redundancy—successful high availability and disaster recovery programs require redundancy or eliminating points of failure. Risk assessment—risk assessment often involves cost comparisons between risks. For example, the risk of an earthquake can be high in some locations and nearly non-existent in others.
What is high availability in performance disaster recovery? ›
Disaster Recovery focuses on recovering from a catastrophic event, such as a natural disaster that destroys the physical Data Center or other infrastructure. It is about having a plan for when the system or network goes down. High Availability focus on smaller, more localized failures or faults.
What is overview of disaster recovery? ›
IT disaster recovery is a portfolio of policies, tools, and processes used to recover or continue operations of critical IT infrastructure, software, and systems after a natural or human-made disaster. The first and foremost aspect of a disaster recovery plan is cloud.
What is high availability vs disaster recovery SQL? ›
SQL Server high availability (HA) is about providing service availability and 100% uptime through redundant and fault-tolerant components at the same location. Disaster Recovery (DR) is about providing service continuity and minimizing downtime through redundant & independent site in a distinct location.
Which of the following is a high availability and disaster recovery solution available in SQL Server 2012? ›
This last (hooray) method is a feature which was first introduced to SQL Server in 2012 to help customers maximize availability for one or more databases. The Availability Groups feature is a High Availability and disaster-recovery solution that provides an enterprise-level alternative to Mirroring.
What are the 4 C's of disaster recovery? ›
In summary, the 4 C's of disaster recovery - Communication, Coordination, Continuity, and Collaboration - serve as the cornerstone of effective disaster preparedness and response. When faced with challenges such as fire and water damage, swift action is imperative.
How do you achieve high availability? ›
One of the most effective strategies for achieving high availability is redundancy and replication. By duplicating critical components or entire systems, organizations can ensure that if one fails, the redundant system takes over seamlessly, avoiding any interruption in service.
What are high availability and disaster recovery concepts? ›
High availability works with either local disk failover on DAS or SSD, or shared disk storage such as SAN, Amazon S3, or HDFS. Disaster recovery protects against failures of an entire data center (power outages, natural disasters, etc.).
A disaster recovery (DR) site is a facility an organization can use to recover and restore its technology infrastructure and operations when its primary data center becomes unavailable.
What are the 4 pillars of disaster recovery? ›
disaster recovery includes physical, environmental and economic elements, as well as psychosocial wellbeing. Recovery can provide an opportunity to improve these aspects beyond previous conditions, by enhancing social and natural environments, infrastructure and economies – contributing to a more resilient community.
What are the 4 phases of disaster recovery? ›
Emergency managers think of disasters as recurring events with four phases: Mitigation, Preparedness, Response, and Recovery.
What is the difference between Azure high availability and disaster recovery? ›
HA is a critical component of DR planning. DR is the process of recovering from a disaster and restoring business operations to a normal state. DR is a subset of BC, which is the process of maintaining business functions or quickly resuming them in the event of a major disruption.
