Study guide
13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database
OCI 2026 Architect Professional 1Z0-997-26
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Architecture Foundations
1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs
2 Chapter 2: High Availability & Resilient Design
2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)
3 Chapter 3: Full Stack Disaster Recovery
3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness
4 Chapter 4: Container Instances, OCIR & OCI DevOps
4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies
5 Chapter 5: OCI Kubernetes Engine (OKE)
5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage
6 Chapter 6: Serverless Functions & API Gateway
6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans
7 Chapter 7: Messaging & Event-Driven Design
7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out
8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager
8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints
9 Chapter 9: Identity & Multi-Tenancy Governance
9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas
10 Chapter 10: Security Posture with Cloud Guard & Security Zones
10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning
11 Chapter 11: Secure Access & Network Protection
11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT
12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault
12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation
13 Chapter 13: Base Database Service & Autonomous AI Database
13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database
14 Chapter 14: Recovery Service, Global Distribution & OCI Cache
14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication
15 Chapter 15: Monitoring, Alarms & Notifications
15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery
16 Chapter 16: Logging, Audit, Connector Hub & Search
16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability
13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database
Key Takeaways Explain This Topic AI
Every Autonomous AI Database Serverless instance has a local Backup-Based Disaster Recovery peer by default.
A local Autonomous Data Guard standby provides automatic failover with a two-minute RTO and zero data loss by default.
A cross-region Autonomous Data Guard standby supports switchover and manual failover with an RTO under 10 minutes, but no automatic failover.
Manual failover to a cross-region Autonomous Data Guard standby has an RPO of up to one minute.
A cross-region peer can be converted to a snapshot standby for up to 48 hours, and changes made on it are discarded when it reconnects.
Last updated: October 2026
Choosing a Disaster Recovery Option
Autonomous AI Database Serverless gives you a menu of disaster recovery (DR) options, each with its own RTO, RPO, and cost. Oracle describes the choices this way:
By default , every database has a local Backup-Based Disaster Recovery peer .
To add automatic failover and lower the RTO, add a local Autonomous Data Guard standby .
For the most resilient setup, add a local Autonomous Data Guard standby and one or more cross-region Autonomous Data Guard standbys .
For a lower-cost regional option with a higher RTO, add a cross-region Backup-Based Disaster Recovery peer .
Option Failover RTO RPO
Local Autonomous Data Guard Automatic or manual; switchover 2 minutes 0 (automatic failover is zero data loss by default)
Cross-region Autonomous Data Guard Manual failover or switchover; no automatic failover Under 10 minutes 0 for switchover; up to 1 minute for manual failover
Backup-Based Disaster Recovery (local or cross-region) Manual, by restoring from backups 1 hour + 1 hour per 5 TB Under 10 seconds local; 1 minute cross-region
Local Autonomous Data Guard Standby
When you enable a local standby, Autonomous AI Database provisions an identical standby in the same region:
In regions with more than one availability domain , the standby is in a different AD .
In single-AD regions , it is in a different fault domain (a different physical machine).
You cannot connect to a local standby . You perform operations such as scaling ECPUs or enabling auto scaling on the primary, and Autonomous Data Guard mirrors them on the standby. After a local failover or switchover, client applications keep the same connection strings and wallets , the private endpoint and ACLs carry over, and APIs and scripts keep working. Oracle recommends a regional subnet for private endpoints for the best availability.
Zero data loss protection. Redo is sent synchronously to the local standby, and the primary does not commit until the standby acknowledges receipt. If acknowledgments are delayed (for example by a network problem), the standby can temporarily fall back to asynchronous transport to protect primary availability. This protection is included at no extra cost.
Automatic failover and the data loss limit. Automatic failover is configured by default to require zero data loss . You can set a data loss limit between 0 and 3,600 seconds . If Autonomous Data Guard determines that the potential data loss would exceed the limit, it does not fail over automatically, and you can choose a manual failover. After a local failover completes, a new local standby is created automatically.
Cost. A local standby adds the cost of the primary's base CPUs and storage, billed on the primary.
Cross-Region and Cross-Tenancy Standbys
A cross-region standby protects against the loss of a whole region. With the ECPU model you can add multiple cross-region peers, one per paired region . A standby can also live in a different tenancy , in the same or another region, which adds isolation (for example against ransomware) and can be used to migrate a database between tenancies.
Key differences from a local standby:
No automatic failover. If the primary and the local standby are unavailable, you manually fail over to the cross-region standby.
You cannot connect to a cross-region standby while it is a standby, and it is not available for read-only queries.
Connection strings and wallets contain only the hostname of their own database. After a cross-region switchover or failover, applications must use the wallet or connection string from the new primary, or connection strings that you build manually with both hostnames. Oracle recommends failing over the mid-tier with the database to avoid cross-region latency, which is a job for Full Stack DR .
Private endpoints, network ACLs, and tags can be configured independently on the remote peer. For private endpoints in different VCNs, cross-region wallets need remote VCN peering and DNS forwarding .
Tool URLs (Database Actions, APEX, ORDS) change after a cross-region role change.
Customer-managed keys require the Vault key to be replicated to the standby region; because a vault replicates to only one region, CMK supports only a single cross-region standby.
Cost: base CPUs plus twice the primary's storage, billed on the remote peer.
Backups With a Cross-Region Standby
Automatic backups are taken only on the database in the primary role . By default they are not replicated. When you enable cross-region backup replication , up to 7 days of automatic backups are copied to the standby region so you can restore or clone there after a role change.
Backup-Based Disaster Recovery
Backup-Based Disaster Recovery uses backups instead of a running standby. The local peer costs nothing beyond automatic backup storage. A cross-region peer is billed for twice the replicated backup storage. Choose it when an RTO of hours is acceptable and a standby's CPU cost is not justified.
Snapshot Standby for DR Testing
A cross-region peer, whether an Autonomous Data Guard standby or a Backup-Based Disaster Recovery peer, can be converted to a snapshot standby . A local peer cannot. The snapshot standby is a read-write database for up to two days (48 hours) :
Redo from the primary is still sent to the region, keeping you protected, but it is not applied until the snapshot standby reconnects.
On reconnect, manually or automatically at 48 hours, all changes made on the snapshot standby are discarded and the accumulated primary changes are applied.
The primary has no downtime during conversion or reconnection, which makes snapshot standbys useful for testing the DR environment, including mid-tier configuration, without a switchover.
Autonomous Data Guard on Dedicated Exadata Infrastructure
On Dedicated Exadata Infrastructure, Autonomous Data Guard is enabled on the Autonomous Container Database (ACD) , so it protects every database in the container:
Protection mode : Maximum Performance (default, asynchronous) or Maximum Availability (synchronous).
Automatic failover (fast-start failover) can be enabled. In Maximum Performance mode, the fast-start failover lag limit defaults to 30 seconds and can be set from 5 to 3,600 seconds , bounding data loss before an automatic failover.
When a configuration has a local standby and a remote one, the local standby is preferred as the automatic failover target.
Operations include switchover, failover, reinstating a disabled standby, and converting the standby ACD to a snapshot standby.