You can enable Autonomous Data Guard with a cross-region standby when Autonomous Database is available (Lifecycle State shows Available).
To add a standby database you must have adequate available resources. Adding an Autonomous Data Guard standby database will only be successful if adding the standby database does not cause you to exceed your Tenancy or compartment limits for CPU and Storage.
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 add a cross-region Autonomous Data Guard standby:
- On the Autonomous Database Details page, under Resources, click Disaster recovery.
- Under Disaster recovery, click Add peer database.
- In the Region field, select a region.
The region list shows the available remote regions where you can create a cross-region standby. When you add a standby database, the list of available regions only shows a remote region if your tenancy is subscribed to the remote region (you must be subscribed to the paired remote region). See Autonomous Database Cross-Region Paired Regions for more information.
- When you select a region, Autonomous Database shows the Select a compartment list. From this list, choose a compartment for the cross-region standby.
- Select the disaster recovery type. In addition, when the source database is
configured with a private endpoint, enter the private endpoint information for
- Select the disaster recovery type: Autonomous Data Guard.
- When the source database is configured with a private endpoint, in the
Network access for standby area enter the
Virtual cloud network and the
In these Network access for standby fields you specify the private endpoint's VCN and Subnet on the remote region where the standby is created.
Note:If you change your network access on the source database to enable a private endpoint after the standby is created, you must manually access the standby to enable a private endpoint on the peer.
- Click Add peer database.
The Autonomous Database Lifecycle state shows Updating. In the Resources area with Disaster recovery selected, the State field shows Provisioning.
After some time, the Lifecycle state shows Available and the standby database provisioning continues.
Note:While you add a standby database, the primary database is available for read/write operations. There is no downtime on the primary database.
When provisioning completes, on the Autonomous Database Details page under Disaster recovery the Oracle Cloud Infrastructure Console shows the following:
Role shows Primary
The Local field shows either Backup-based or Autonomous Data Guard. When the local field shows Backup-based, there is also a link, Upgrade to Autonomous Data Guard. Click this link to upgrade your local disaster recovery to Autonomous Data Guard.
The Cross-region field shows Autonomous Data Guard.
Description of the illustration adb_data_guard_console_state.png
When you enable a cross-region standby, the standby database created in the remote region has the same display name as the primary database with the extension: "_Remote".
When you click Disaster recovery under Resources, the Peer Autonomous Database column shows the standby database name and a provides a link. Click the link to go to the Oracle Cloud Infrastructure Console for the remote standby database.
Notes for adding a cross-region standby database:
Autonomous Database generates the Enable cross-region disaster recovery work request. To view the request, under Resources click Work requests.
After you add a cross-region (remote) standby database, the wallet and connection string from the primary database will contain only the hostname of the primary database, and the wallet and connection string from the remote database will contain only the hostname of the remote database. This applies for both instance and regional wallets.
See Cross-Region Disaster Recovery Connection Strings and Wallets for more information.
While you add a standby database and the Lifecycle State 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.
See Cross-Region Autonomous Data Guard Notes and Notes for Customer-Managed Keys with Autonomous Data Guard for information on using customer-managed keys and for additional notes for using Autonomous Data Guard with a cross-region standby.