Study guide
14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock
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
14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock
Key Takeaways Explain This Topic AI
Autonomous Recovery Service is based on Oracle Zero Data Loss Recovery Appliance technology and is Oracle's recommended destination for Oracle-managed automatic database backups.
Recovery Service uses an incremental-forever backup approach, which removes the need for weekly full backups.
Oracle-defined protection policies retain backups for 14 days (Bronze), 35 days (Silver), 65 days (Gold), or 95 days (Platinum).
Real-Time Protection continuously sends redo to Recovery Service, allowing recovery to within less than a second of an outage, as a premium option.
With retention lock enabled on a protection policy, nobody can modify or delete backups until the retention period expires.
Last updated: October 2026
What Autonomous Recovery Service Is
Oracle Database Zero Data Loss Autonomous Recovery Service , usually called Autonomous Recovery Service or Recovery Service , is a fully managed service built on the technology of the on-premises Oracle Zero Data Loss Recovery Appliance (ZDLRA) . It protects Oracle databases running on:
- Exadata Database Service on Dedicated Infrastructure and on Exascale Infrastructure
- Oracle Base Database Service
- Oracle Database@AWS , Oracle Database@Azure , and Oracle Database@Google Cloud
- On-premises databases, through Oracle Database Zero Data Loss Cloud Protect
Oracle recommends selecting Recovery Service as the destination for Oracle-managed automatic backups of these cloud databases. Autonomous AI Database is not on this list because it manages its own automatic backups, as covered in Chapter 13.
Why Use It Instead of Object Storage Backups
Capability What it means
Incremental-forever backups After the first backup, only changed blocks are sent and the service builds virtual full backups. Weekly full backups are no longer needed, which reduces database CPU, memory, I/O, and the backup window.
Backup validation All backups are validated for data anomalies that could affect recovery.
Immutability and enforced encryption Backups cannot be altered by anyone in the tenancy and are always encrypted, which matters for ransomware protection.
Central protection dashboard Shows whether backups are healthy, how long since the last backup, how far back you can recover, and how much space backups use.
Real-Time Protection (premium) Continuous redo shipping that allows recovery to within less than a second of an outage or attack.
Without Real-Time Protection, Recovery Service backups cost the same as Object Storage backups. Real-Time Protection is the premium Zero Data Loss option. It continuously transfers redo changes to the service, giving an RPO near zero, instead of losing everything since the last scheduled backup.
Protection Policies
A protection policy sets the backup retention period for the databases that use it.
- Oracle-defined policy Retention
- Bronze 14 days
- Silver 35 days
- Gold 65 days
- Platinum 95 days
Oracle-defined policies cannot be modified. You can create custom policies with a retention period from 14 to 95 days . Long-term retention (LTR) backups for compliance are created through the database service and are kept for their own specified retention period.
Retention Lock
A custom protection policy can enable a retention lock . After the lock takes effect, following a minimum 14-day delay, the retention period can only be increased, and nobody can modify or delete backups until the retention period expires , including tenancy administrators. With a lock in place, terminating a database or disabling its automatic backups does not delete the backups early; they are deleted only after the retention period ends.
Multicloud Backup Location
For Oracle Database@AWS, @Azure, and @Google Cloud, you can choose to store backups in the same cloud as the database, for example to meet data residency rules.
Enabling Backups and the Protected Database Resource
When you enable automatic backups for a database with Recovery Service as the destination, you choose a protection policy, decide whether to enable Real-Time Protection, and choose a deletion option :
Retain backups according to the protection policy retention period after the database is terminated.
Retain backups for 72 hours, then delete.
Recovery Service then creates a protected database resource that represents the database. Its Health shows Protected , Warning , or Alert , and its details show the recovery window and space used. When a database is terminated, its protected database enters the Delete Scheduled state until the chosen delay ends.
Network and IAM Prerequisites
Recovery Service connects to the database through a Recovery Service subnet that you register in the database VCN:
Use a private subnet (recommended), IPv4 only. Oracle recommends a /24 size.
Allow stateful ingress on TCP ports 8005 and 2484 from the database, using security lists or up to five NSGs.
Register the subnet as a Recovery Service subnet resource.
Add the IAM policy that lets the service manage the networking it needs: Allow service rcs to manage virtual-network-family in tenancy .
Designing Backup and Recovery With Recovery Service
- Requirement Design choice
- Lose as little data as possible during ransomware or a site outage Enable Real-Time Protection
- Backups that even administrators cannot delete Custom policy with retention lock
- 90-day recovery window Platinum (95 days) or a custom policy
- Lower backup overhead on busy databases Incremental-forever backups offloaded to Recovery Service
Regional disaster recovery with a running standby Data Guard or Full Stack DR; backups are not a replacement for a standby
Recovery Service is about recoverability : restoring a database to a point in time after corruption, deletion, or attack. Fast regional failover still comes from Data Guard standbys and Full Stack DR.