Enable Autonomous Data Guard

To enable Autonomous Data Guard you update the disaster recovery type to use a standby database.

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 Cloud.
From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then click Autonomous Database.
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 information tab, in the Disaster recovery area, click at the end of the Local field and select Upgrade to Autonomous Data Guard.

Description of the illustration adb_add_data_guard.png

This shows the Update disaster recovery page.
Select Autonomous Data Guard.

Description of the illustration adb_update_dr_type_data_guard.png
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, on the details page, select the Work requests tab.

You may need to wait for the work request to complete to 100% before you see Autonomous Data Guard in the DR type column on the Disaster recovery tab. 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.

Parent topic: Use Standby Databases with Autonomous Data Guard for Disaster Recovery