Enterprise 11: Re-establish a duplicate DR site
- Zuletzt aktualisiert2022/08/11
Enterprise 11: Re-establish a duplicate DR site
After a secondary (backup) site is recovered as the primary (production) site, establish a new secondary DR site.
Prerequisites
The recovery site is up and running as the new production site.
The process of returning activity to a primary (active) production site, plus secondary (backup) site depends on the state of the original primary site.
Procedure
-
If the old production environment becomes available again, complete the following to
switch back to the original DR primary site.
-
If the old DR primary production environment is rendered completely unusable
due to the disaster, re-establish a new secondary (standby) DR site. Complete
the recovery DR steps to re-establish primary and secondary DR sites.
Next steps
No additional steps are required. The DR primary and secondary sites are restored.
- The bot Activation utility does not need to be run again. Activation occurs when Automation Anywhere is first deployed to the DR cluster sites only.
- For any subsequent disasters, only the database query needs to be run on DR secondary (standby) Control Room database. This is required because the replication between DR primary (production) and DR secondary (standby) overwrites DR secondary site Bot Runner data in DR secondary site database with DR primary (production) Bot Runner data.
- Similarly, the mapping between DR primary and DR secondary Bot Runner is established. Use the same mapping for all subsequent disasters or mock drills.