Quick Into: Automatic failover for Autonomous Data Guard enabled Autonomous Databases on Exadata Cloud at Customer and Dedicated Infrastructure
There is a very good blog post by Ranganath Srirangapatna Ramachandra Principal Product Manager at Oracle on Automatic failover for Autonomous Data Guard enabled Autonomous Databases on Exadata Cloud at Customer and Dedicated Infrastructure.Here is a quick recap.
- Automatic failover AKA Fast-start Failover in Oracle Data Guard.
- Automatic Failover allows Autonomous Data Guard to automatically fail over to your standby Autonomous database in the event of an outage on your primary database.
- Automatic failover rapidly fails over the standby Autonomous database to the primary database role without requiring any manual steps.
- Automatic failover is optional and can be enabled/disabled on your Autonomous Container Databases with Autonomous Data Guard.
- Both maximum performance and maximum availability protection modes are available with automatic failover.
- Automatic failover guarantees zero data loss in Maximum Availability mode.
- Automatic failover ensures no data is lost that is more than the amount of data (in seconds) specified by the FastStartFailoverLagLimit configuration property in Maximum Performance mode.
- FastStartFailoverLagLimit is set to 30 seconds and applies only to maximum performance mode. Automatic failover is only possible when the configured data loss guarantee can be upheld.
- Oracle automatically troubleshoots and repairs the failure conditions related to the primary database and reinstates it to the standby database role after an automatic failover occurs.
- You can perform a switchover operation to change the database roles to the original state after the failed primary is reinstated to the standby database.
Enjoy this blog post on Automatic failover for Autonomous Data Guard enabled Autonomous Databases on Exadata Cloud at Customer and Dedicated Infrastructure.
Cheers.
