In addition to a local Backup-Based Disaster Recovery peer, you can add one or more remote region (cross-region) Backup-Based Disaster Recovery peers.

1. On the Autonomous Database Details page, under Disaster recovery, in the Cross-region field, click Add peer database, alternatively in the Resources area click Disaster recovery.
   
   

   
   Description of the illustration adb_bbdr_ui_update.png

   
   

   
   Description of the illustration adb_backup_copy_resources.png
2. Click Add peer database.
3. In the Region drop-down list, select a region.

   The region list shows the available remote regions where you can create a cross-region peer. When you add a peer 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.

4. In the Select a compartment drop-down list, select a compartment.
5. Select the disaster recovery type. In addition, when the source database is configured with a private endpoint, enter the private endpoint information for the peer.
   1. Select the disaster recovery type: Backup-based disaster recovery.
   2. If you want to enable Cross-Region Backup Replication select the Enable cross-region backup replication to disaster recovery peer check-box. See Replicating Backups to a Cross-Region Backup Based Disaster Recovery Peer for more information.
      
      

      
      Description of the illustration adbs_bbdr_cross_region_replication.png

      
      
   3. When the source database is configured with a private endpoint, in the Network access for standby area enter the Virtual cloud network and the Subnet.
      
      Description of the illustration adb_create_cross_region_peer_private_endpoint.png

      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. Configure Private Endpoints.

      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.
6. Click Add peer database.

   The Autonomous Database Lifecycle state changes to Updating. In the Resources area, the number next to Disaster recovery increments to show that you have another disaster recovery peer, and the State field shows Provisioning for the new cross-region peer.

   Note
   
   While you add a new peer, the primary database is available for read/write operations. There is no downtime on the primary database.

   Autonomous Database generates a work request when you add a cross-region peer To view the work request, under Resources click Work Requests.

1. On the Autonomous Database Details page, in the Resources area select Disaster recovery.
2. In a row that lists a cross-region standby, click at the end of the row and select Update disaster recovery.

   This shows the Update disaster recovery page.

   
   

   
   Description of the illustration adb_bbdr_update_backup_replication.png

   
   
3. Enable or disable backup replication.
   1. If cross-region backup replication is disabled, select Enable cross-region backup replication to disaster recovery peer to enable the option.
   2. If cross-region backup replication is enabled, deselect Enable cross-region backup replication to disaster recovery peer to disable the option.
4. Click Submit.

   The Autonomous Database Lifecycle state changes to Updating.

A cross-region Backup-Based Disaster Recovery peer can be converted to a snapshot standby. This converts the peer to a read-write database for up to two days.

See Convert Cross-Region Peer to Snapshot Standby for more information.

Shows you the steps to disconnect a cross-region Backup-Based Disaster Recovery peer from the Primary database.

Describes the steps to terminate a cross-region (remote) peer.

1. On the Primary database, on the Autonomous Database Details page under Resources, select Disaster recovery.
2. Access the Oracle Cloud Infrastructure Console for the remote region peer.

   The Disaster recovery information area shows the Peer Autonomous Database. The remote peer has the same display name as the primary database, with an "_region" extension. Where region is the region name, such as IAD or BOM.

   If you created the cross-region peer before the introduction of support for multiple cross-region peers, the remote peer has the same display name as the primary database, with an "_Remote" extension.

   Under Peer Autonomous Database, click the link for the remote peer to access the cross-region peer.

3. On the Oracle Cloud Infrastructure Console for the remote peer, on the Details page, from the More actions drop-down list, select Terminate.
4. On the Terminate Autonomous Database page, enter the database name to confirm that you want to terminate the cross-region peer.
5. Click Terminate Autonomous Database.

   While the peer is terminating, the Lifecycle state changes to Terminating.

1. On the primary database, on the Autonomous Database Details page, under Resources select Disaster recovery.
2. Access the remote peer.

   The Disaster recovery information area shows the Peer Autonomous Database. The remote peer database by default has the same display name as the primary database, with an extension. For example, DBNAME_remote.

   Under Peer Autonomous Database, click the link to access a cross-region peer.

3. On the remote peer database, edit the access control list.

   Before you change ACL the dialog shows a message indicating that ACLs on the peer database are syncing from the Primary database. For example:

   
   Description of the illustration adb_remote_peer_sync_acls.png

   See Configure Access Control Lists for an Existing Autonomous Database Instance for more information.

4. Add, remove, or modify one or more ACLs.
5. Click Save.

Lists notes and restrictions for adding and managing a cross-region Backup-Based Disaster Recovery peer.

• After you add a cross-region (remote) peer, 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 to both instance and regional wallets.

  See Cross-Region Disaster Recovery Connection Strings and Wallets for more information.

• If you enable the option Enable cross-region backup replication to disaster recovery peer, it can take between several minutes and several hours to replicate the backups to the remote region, depending on the size of the backups. After backups are replicated, when you select Backups under Resources on the peer database's Oracle Cloud Infrastructure Console, you will see the list of replicated backups.

  See Enable or Disable Backup Replication for an Existing Cross-Region Peer for more information.

• When you add a cross region peer there are special considerations when the primary instance is using customer-managed keys, or if you want to switch to use customer-managed keys. See Autonomous Data Guard with Customer Managed Keys for more information.

• When you add a Backup-Based Disaster Recovery peer, while the Lifecycle state field shows Updating, the following actions are disabled on 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.