Can I failback an Aurora DB cluster to its original Region after a cross-Region failover?
If I set up cross-Region replication for my Aurora DB cluster, can I failback the Aurora DB cluster to its original AWS Region after a cross-Region failover?
Also, if that's possible, how do I make sure that any new data that was added to the DB cluster during the service interruption is replicated and synced back to the original Region?
- Newest
- Most votes
- Most comments
After a cross-Region failover occurs, failback to the original Region isn't possible. The promoted Region (the old secondary Region) acts as the new primary Aurora DB cluster. To return the new primary Aurora DB cluster in this scenario to it's original Region, you must create a new read replica of the new primary Aurora DB cluster and then manually perform a failover to the original Region.
For more information, see Recovering an Amazon Aurora global database from an unplanned outage.
managed planned failover now allows you to fail over and fail back.
With this managed planned failover capability, you can repeatedly change which AWS Region hosts the primary cluster while preserving the physical topology of your global database and avoiding unnecessary application changes. Aurora Global Database managed planned fail over simplifies the planned fail over process in scenarios like rotating the primary region for regulatory compliance or disaster recovery exercises.
However you can only use managed planned failover on a healthy Aurora global database. To recover from an unplanned outage, follow the "detach and promote" process detailed in Recovering an Amazon Aurora global database from an unplanned outage.
Relevant content
- Accepted Answer
- Accepted Answerasked a year ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
