- Knowledge Base
- Oracle Cloud Infrastructure
- OCI Autonomous AI Database
- Enable Disaster Recovery for Autonomous AI Databases
Enable cross-region disaster recovery for your OCI Autonomous AI Databases in order to ensure business continuity and protect database instances with peer databases in separate OCI regions.
Cross-region disaster recovery protects against data loss if there's a regional outage or a complete data failure in the primary region by providing a geographically isolated standby database. This strategy ensures business continuity and high availability by enabling a rapid, seamless switchover or failover to the remote peer instance.
Audit
To determine if cross-region disaster recovery is enabled for your Oracle Cloud Infrastructure (OCI) Autonomous AI Databases, perform the following operations:
Using OCI Console
-
Sign in to your Oracle Cloud Infrastructure (OCI) account.
-
Navigate to Autonomous AI Databases console available at https://cloud.oracle.com/db/adbs.
-
For Applied filters, choose an OCI compartment from the Compartment dropdown menu, to list the Autonomous AI Databases provisioned in the selected compartment.
-
Click on the name (link) of the Autonomous AI Database that you want to examine, listed in the Display Name column.
-
Select the Autonomous AI Database information tab, and check the Cross-region feature status, listed in the Disaster recovery section. If Cross-region is set to Not enabled, cross-region disaster recovery is disabled for the selected Oracle Cloud Infrastructure (OCI) Autonomous AI Database.
Using OCI CLI
-
Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:
oci iam compartment list --all --include-root --query 'data[]."id"'
-
The command output should return the requested OCI compartment identifiers (OCIDs):
[ "ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd", "ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd" ]
-
Run db autonomous-database list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, to list the ID of each Autonomous AI Database provisioned in the selected OCI compartment:
oci db autonomous-database list --compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd' --all --query 'data[]."id"'
-
The command output should return the requested database instance IDs:
[ "ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd", "ocid1.autonomousdatabase.oc1.ap-sydney-1.abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd" ]
-
Run db autonomous-database get command (Windows/macOS/Linux) with the ID of the Autonomous AI Database that you want to examine as the identifier parameter and custom output filters to determine if cross-region disaster recovery is enabled for the selected database instance:
oci db autonomous-database get --autonomous-database-id 'ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd' --query 'data.{"peer-db-ids":"peer-db-ids"}' -
The command output should return the ID(s) of the peer database(s) created for the selected database instance:
{ "peer-db-ids": null }If the db autonomous-database get command output returns null for the "peer-db-ids" property, as shown in the output example above, there are no peer databases created for your database instance. As a result, cross-region disaster recovery is not enabled for the selected OCI Autonomous AI Database.
Remediation / Resolution
To ensure that cross-region disaster recovery is enabled and configured for your Oracle Cloud Infrastructure (OCI) Autonomous AI Databases, perform the following operations:
Using OCI Console
-
Sign in to your Oracle Cloud Infrastructure (OCI) account.
-
Navigate to Autonomous AI Databases console available at https://cloud.oracle.com/db/adbs.
-
For Applied filters, choose an OCI compartment from the Compartment dropdown menu, to list the Autonomous AI Databases provisioned in the selected compartment.
-
Click on the name (link) of the Autonomous AI Database that you want to configure, listed in the Display Name column.
-
Select the Disaster recovery tab, choose Add peer database, and perform the following actions to enable and configure cross-region disaster recovery for the selected Autonomous AI Database:
- Select the preferred region from the Region dropdown list. The Region list shows the available remote regions where you can create a cross-region standby.
- For Compartment, choose the OCI compartment for the cross-region standby.
- Under Disaster recovery, select the disaster recovery type (Autonomous Data Guard or Backup-based disaster recovery).
- (Optional) To enable cross-region backup replication to disaster recovery peer, switch on the the Enable cross-region backup replication to disaster recovery peer.
- (Optional) Choose Advanced options and use the Tagging controls to add free-form and/or defined tags to the new OCI resource.
- Choose Add to create the peer database. This will enable cross-region disaster recovery for the selected OCI Autonomous AI Database. Once the process is complete, the peer database State should change from Provisioning to Standby.
Using OCI CLI
-
Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:
oci iam compartment list --all --include-root --query 'data[]."id"'
-
The command output should return the requested OCI compartment identifiers (OCIDs):
[ "ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd", "ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd" ]
-
Run db autonomous-database list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, to list the ID of each Autonomous AI Database provisioned in the selected OCI compartment:
oci db autonomous-database list --compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd' --all --query 'data[]."id"'
-
The command output should return the requested database instance IDs:
[ "ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd", "ocid1.autonomousdatabase.oc1.ap-sydney-1.abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd" ]
-
Run db autonomous-database create-autonomous-database-create-cross-region-disaster-recovery-details command (Windows/macOS/Linux) to create the peer database necessary to enable cross-region disaster recovery for the selected OCI Autonomous AI Database. For --source-id, specify the ID of the database instance that will be used to create a new peer database for the DR association. For --region, specify the remote region where to create the cross-region standby. For --remote-disaster-recovery-type, select the disaster recovery type, 'ADG' for Autonomous Data Guard or 'BACKUP_BASED' for Backup-based disaster recovery:
oci db autonomous-database create-autonomous-database-create-cross-region-disaster-recovery-details --compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd' --remote-disaster-recovery-type 'BACKUP_BASED' --region 'ap-melbourne-1' --source-id 'ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
-
The command output should return the configuration information available for the peer database instance:
{ "data": { "allocated-storage-size-in-tbs": 0.0078125, "are-primary-whitelisted-ips-used": null, "auto-refresh-frequency-in-seconds": null, "auto-refresh-point-lag-in-seconds": null, "autonomous-container-database-id": null, "autonomous-maintenance-schedule-type": "REGULAR", "availability-domain": "ABCD:AP-SYDNEY-1-AD-1", "failed-data-recovery-in-seconds": null, "freeform-tags": {}, "id": "ocid1.autonomousdatabase.oc1.ap-sydney-1.abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd", "in-memory-area-in-gbs": null, "in-memory-percentage": null, "infrastructure-type": null, "is-access-control-enabled": null, "is-auto-scaling-enabled": true, "is-auto-scaling-for-storage-enabled": true, "is-backup-retention-locked": false, "is-data-guard-enabled": true, "is-dedicated": false, "is-dev-tier": null, "is-free-tier": false, "is-local-data-guard-enabled": false, "is-mtls-connection-required": true, "is-preview": false, "is-reconnect-clone-enabled": false, "is-refreshable-clone": null, "is-remote-data-guard-enabled": false, "key-store-wallet-name": null, "kms-key-id": "ORACLE_MANAGED_KEY", ... "license-model": "LICENSE_INCLUDED", "lifecycle-details": null, "lifecycle-state": "UPDATING", "local-adg-auto-failover-max-data-loss-limit": null, "local-disaster-recovery-type": "BACKUP_BASED", "time-data-guard-role-changed": null, "time-deletion-of-free-autonomous-database": null, "time-disaster-recovery-role-changed": null, "time-earliest-available-db-version-upgrade": "2025-12-13T14:10:00+00:00", "time-latest-available-db-version-upgrade": "2025-12-13T13:40:00+00:00", "time-local-data-guard-enabled": "2025-12-13T09:27:58.721000+00:00", "time-maintenance-begin": "2025-12-15T06:00:00+00:00", "time-maintenance-end": "2025-12-15T08:00:00+00:00", "time-of-auto-refresh-start": null, "time-of-joining-resource-pool": null, "time-of-last-failover": null, "time-of-last-refresh": null, "time-of-last-refresh-point": null, "time-of-last-switchover": null, "time-of-next-refresh": null, "time-reclamation-of-free-autonomous-database": null, "time-scheduled-db-version-upgrade": null, "time-undeleted": null, "time-until-reconnect-clone-enabled": null, "total-backup-storage-size-in-gbs": 0.0, "used-data-storage-size-in-gbs": null, "used-data-storage-size-in-tbs": null, "vanity-connection-urls": null, }, "etag": "abcd1234", "opc-work-request-id": "ocid1.coreservicesworkrequest.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd" }
References
- Oracle Cloud Infrastructure Documentation
- High Availability
- Add a Cross-Region Standby Database
- Use Backup-Based Disaster Recovery
- Manage the Service
- Oracle Cloud Infrastructure CLI Documentation
- compartment list
- autonomous-database list
- autonomous-database get
- create-autonomous-database-create-cross-region-disaster-recovery-details