Use Standby Databases with Autonomous Data Guard for Disaster Recovery
Autonomous Database Disaster Recovery Options
Autonomous Data Guard When you add an Autonomous Data Guard standby database, the system creates a standby database that continuously gets updated with the changes from the primary database. You can use Autonomous Data Guard with a standby in the current region, a local standby, or with a standby in a different region, a cross-region standby. You can also use Autonomous Data Guard with both a local standby and a cross-region standby.
Autonomous Data Guard is available for the following workload types:
- Data Warehouse
- Transaction Processing
Backup-Based Disaster Recovery uses backups to instantiate a peer database at the time of switchover or failover. This enables you to have a lower cost and higher Recovery Time Objective (RTO) disaster recovery option for your Autonomous Database, as compared with Autonomous Data Guard. For local backup-based disaster recovery, existing local backups are utilized. There are no additional costs for a local Backup-Based Disaster Recovery. Cross-Region Backup-Based Disaster Recovery incurs an additional cost. See Use Backup-Based Disaster Recovery for details on Backup-Based Disaster Recovery.
Backup-Based Disaster Recovery is available for all workload types.
- About Standby Databases
Provides information about enabling and using Autonomous Data Guard for disaster recovery on Autonomous Database. - Enable Autonomous Data Guard
To enable Autonomous Data Guard you update the disaster recovery type to use a standby database. - Add a Cross-Region Standby Database
You can enable Autonomous Data Guard with a cross-region standby when Autonomous Database is available (Lifecycle State shows Available). - Perform a Switchover
When you perform a switchover, the primary database becomes the standby database and the standby database becomes the primary database, with no data loss. - Automatic Failover with a Standby Database
After you add a local Autonomous Data Guard standby database, the system monitors the primary instance and automatically fails over to a local standby database in certain scenarios. - Perform a Manual Failover
When Autonomous Data Guard cannot automatically fail over to a local standby database, if a local standby database is available you can perform a manual failover to make the local standby database the primary database. - Convert Cross Region Peer to Snapshot Standby
A cross-region peer can be converted to a snapshot standby. This converts the peer to a read-write database for up to two days. - Update Standby to Use a Backup Copy Peer
Describes the steps to change the disaster recovery type from Autonomous Data Guard standby database to Backup-Based Disaster Recovery. - Disable a Cross Region Standby Database
Disabling a cross-region Autonomous Data Guard standby database terminates the standby database. If you later add a cross-region Autonomous Data Guard standby, the system creates a new cross-region standby database. - Events and Notifications for a Standby Database
You can use Oracle Cloud Infrastructure Events to be notified of and to specify rules to automatically respond to Autonomous Data Guard operations. - Use the API
Provides links for details on using API operations to manage Autonomous Data Guard. - Autonomous Data Guard Notes
Note the following for using Autonomous Database with an Autonomous Data Guard standby database: - Autonomous Database Cross-Region Paired Regions
Autonomous Database provides paired regions for creating cross-region databases, including cross-region clones and cross-region disaster recovery peers.
Parent topic: High Availability