Disaster Recovery deployment model

The Disaster Recovery (DR) deployment model uses high availability (HA) clusters distributed over a geographic area.

Disaster Recovery (DR) is a method where two high availability (HA) data center configurations are separated geographically. The extra benefit here from a single location HA configuration is that in the event of a localized disaster, the physically removed data center resumes functions with minimum downtime.

Prerequisites

Before performing the IQ Bot DR, review the following prerequisites:

Enable the inbound and outbound ports.
Add all the hostnames in the host file entries for all the nodes.
Ensure that the primary and secondary databases are in sync.
Automation Anywhere Control Room and IQ Bot must be installed on both primary (active) and secondary (passive) DR sites.
While switching between the primary and secondary servers, ensure the following:
- If the secondary database has read-only permission, the primary database has read/write permission.
- If the secondary database has read/write permission, the primary database has read-only permission.

The following diagram shows the IQ Bot DR setup:

IQ Bot disaster recovery

In this example, all the servers have redundancy.

Multiple users have access the IQ Bot cluster through their web browsers. The web browsers communicate to the IQ Bot clusters through the load balancers.
Multiple Bot Runners communicate to their IQ Bot cluster through the load balancer.
The server message block (SMB) file share and the Microsoft SQL Server store data from their IQ Bot cluster. Both servers are asynchronously replicated to the backup disaster recovery site.
Microsoft SQL Server uses redundancy through replication syncing to the clustered Microsoft SQL Server on the primary disaster recovery site.

For disaster recovery in IQ Bot environment.

Deploy a second IQ Bot HA cluster in an additional data center that is in a separate geographic location.
In the event of a primary site failure, do the disaster recovery manually. See Disaster recovery failover steps overview.

注： When a failover to a backup site occurs, it is possible that very recent changes made on the primary site are lost.

Pros: Provides business continuity when faced with data center outage or loss.
Cons: Increased operational burden.

Contact your Customer Success Manager (CSM) or Partner Enablement Manager (PEM) for more information on benchmarking IQ Bot On-Premises.Disaster Recovery.

IQ Bot On-Premises Disaster Recovery benchmarking (A-People login required)

Automation 360