Disaster recovery (DR) provides a recovery solution across a geographically separated sites in the event of a disaster that causes an entire data center to fail.

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. Disaster recovery addresses different causes of failures in a system. It focuses on reestablishing services after an incident.

Recovery of a system includes scenarios such as restarting a service or system and restoring configuration files or a database from backups. The Automation Anywhere implementation of disaster recovery reduces downtime and maintains continuity of business (CoB) for your bot activities.

Enterprise 11 disaster recovery deployment model

Site failures in multisite organizations are caused by natural disasters, power outages, or connectivity outages. DR protect services and data in the event of a disaster. The following is a list of components associated with it.

• Disaster recovery site— This site is an alternative backup site that is used when a primary site becomes unusable due to failure or disaster. It contains equipment and infrastructure that can be temporarily used to manage business processes until the main site's functionality is fully restored.
• Site replication— The secondary (standby) site has the same configuration and software as the primary site and they are duplicate (redundant copy) of the primary. Data is replicated (copied) from the primary site to the secondary (standby) site.
• Database replication— 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.
• Downtime—The time between when the primary site become unavailable or inoperable resulting in an outage for a group of users or entire organizations and the secondary site becomes operational.
• Failover—If one of the primary site fails, the workload of the failed site automatically shifts to the secondary site for disaster recovery. This process is called failover. When failover completes, the secondary site becomes the active site.
• Failback—Restoring operations from the secondary site to the primary site after the primary site is returned to normal. The workload can be failed back from the secondary site to the primary site which again becomes the active site.