Disaster Recovery preparation
Describe the settings and configuration required to ensure recovery in the event of a failed site.
Prior to installing Automation Anywhere, prepare your Disaster Recovery sites.
- Deploy bots
- Deploy Bot task and reference files according to your data center administrator approved local procedures for file and data transfers. Typically, these are deployed to production and standby recovery site in parallel.
- Hardware failure protection
- Deploy multiple Web servers locally on each DR site. Use an active-active method to a assist with load balancing and protect against local hardware failures.
- Data corruption protection
- Perform regular on-site full and daily backups of database server, the Control Room repository, configuration and task files.
- DR sites
- Apply the same storage configuration on both the primary and secondary DR sites. Apply replication methods to update the secondary DR site from the primary DR site. Example content describes using the Windows feature, Distributed File System (DFS).
- Environmental disaster protection
- Geographic separation
- Protect against a geographical or environmental disaster, complete regular backups of the secondary DR site.
- Primary site
- The location where the active cluster resides.
- In the event of a disaster, some events could stop part way through execution. Retrieve task level log files and other intermediate files to identify the state of any pending processes. Example content describes using SQL Server 2012 AlwaysOn Availability Groups.
- The process of shifting the production activities from a failed primary site to the secondary backup site. This applies to DR sites, where recovery is from one site to another.
- Recovery site
- The secondary (redundant) site, that is geographically separated from the primary DR site. This secondary site is a passive/standby replication of the primary site. It is designated as the target location in the event of a disaster.