By default and at no additional cost, Autonomous Database provides a local backup copy peer for each Autonomous Database instance. You enable Autonomous Data Guard by changing the disaster recovery type to use a standby database. Autonomous Data Guard provides a lower Recovery Time Objective (RTO), compared to using a backup copy peer, and provides for automatic failover to a local standby when the primary database is not available.
Note:When you change your disaster recovery type to use a local standby database, you also have the option to add a second cross-region disaster recovery option, either a cross-region Autonomous Data Guard standby database or a cross-region backup copy peer.
Perform the following prerequisite steps as necessary:
Open the Oracle Cloud Infrastructure Console by clicking the next to Oracle Cloud.
From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then, depending on your workload, click one of: Autonomous Data Warehouse or Autonomous Transaction Processing.
On the Autonomous Databases page select your Autonomous Database from the links under the Display Name column.
To change your disaster recovery type to add a local Autonomous Data Guard standby database:
- On the Autonomous Database Details page, in the Resources area select Disaster recovery.
- In the row showing the database's disaster recovery details, click at the end of the row and select Update disaster
This shows the Update disaster recovery page.
- Select Autonomous Data Guard.
- In the Automatic Failover with data loss limit in
seconds field, accept the default data loss limit of 0, or enter
a custom value for the automatic failover data loss limit.
See Automatic Failover with a Standby Database for more information.
- Click Submit.
The Autonomous Database Lifecycle State changes to Updating.
The State column shows Provisioning while Autonomous Database provisions the standby database.
After some time the Lifecycle State shows Available and the standby database provisioning continues.
When provisioning completes the DR Type column shows Autonomous Data Guard.
Note:While you add a new standby database, the primary database is available for read/write operations. There is no downtime on the primary database.
Notes for changing the disaster recovery type to a local Autonomous Data Guard standby database:
Autonomous Database generates an Enable Autonomous Data Guard work request. To view the request, under Resources click Work Requests.
The work request may complete to 100% before you see Autonomous Data Guard in the DR Type column when you select Disaster recovery under Resources. The provisioning process takes several minutes.
While you add a local standby database, when the Lifecycle State field shows Updating, the following actions are disabled for the primary database:
Move Resource. See Move an Autonomous Database to a Different Compartment for information on moving an instance.
Stop. See Stop Autonomous Database for information on stopping an instance.
Restart. See Restart Autonomous Database for information on restarting an instance.
Restore. See Restore and Recover your Autonomous Database for information on restoring.