Warm stand-by
- Updated: 2022/03/10
Warm stand-by
Host two setups or sites - primary and backup for the warm stand-by DR procedure.
Prerequisites
Each setup would have following recommended configurations:
- Automation 360 hosted in clustered mode (three nodes)
- SQL instance
- Repository storage (shared network drive)
- Git repository
Synchronous replication of the data onto the backup node should be configured. The backup node should have the exact same configuration as Primary node; except for Control Room.
- To sync Git repository, back up Git repository path from primary to backup path.
- To sync SQL database, setup replication from primary to backup database.
Once configured the setup scheme would look like this:
![HA for disaster recovery](https://automationanywhere-be-prod.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/deployment-planning/on-prem-install/../../../../cloudarchitecturedrdatacentercluster.png?_LANG=enus)
Complete
the disaster recovery deployment on the two geographically separated sites, where
one site is the primary (active) site and the other is the secondary (passive) site
used for backup. If the primary site cluster fails, perform recovery on the
secondary site.
Note: The secondary site
should be set up as a passive configuration so that the failover procedure can
be performed without delay.
These steps apply to all the servers in the Automation 360 cluster, including the Control Room servers, SQL server, and Elasticsearch server.