Lesen und beachten Sie die Automation Anywhere-Dokumentation

Automation Anywhere Version 11.3

Inhalt schließen

Inhalte

Inhalt öffnen

Enterprise 11 disaster recovery deployment model

  • Aktualisiert: 2022/08/10
    • 11.3.x
    • Erkunden
    • Enterprise

Enterprise 11 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 the two High Availability (HA) data center configurations are separated geographically. The extra benefit here from a single location HA configuration, is in the event of a localized disaster, the physically removed data center can resume functions with minimum downtime.

HA for Disaster Recovery
In this example, all the servers have HA redundancy. Every data center component, including the PostgreSQL server and Subversion (SVN) server, that do not necessarily require HA redundancy. See Graceful Degradation for bot support if either of these fail.
Note: Automation Anywhere does not support stretch clusters. Ensure that all the HA cluster nodes are configured in the same location. Do not configure the nodes in a single HA cluster which is located across various DR sites. Ensure that you configure one HA cluster at the primary DR site, and the other HA cluster at the secondary DR site.

For disaster recovery in Automation Anywhere environment.

  • Deploy a second Control Room HA cluster in an additional datacenter that is in a separate geographic location.

  • In the event of a primary site failure, perform the disaster recovery manually. See the Enterprise 11 disaster recovery failover steps overview.

    Note: When a failover to a backup site occurs, very recent changes made on the primary site might be lost.

Pros: Provides business continuity when faced with datacenter outage or loss.

Cons: Increased operational burden.

Feedback senden