Study guide
2.3 Block Volume Replication, Volume Groups & Backup Policies
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
2.3 Block Volume Replication, Volume Groups & Backup Policies
Key Takeaways Explain This Topic AI
The Block Volume service is designed for 99.99% annual durability for block and boot volumes, so Oracle still recommends regular backups.
Block Volume replication is asynchronous; Oracle's typical cross-region RPO target is under 30 minutes, but heavy write activity can push it above an hour.
Activating a volume or volume group replica creates a new volume or volume group by cloning the replica; activate the volume group replica to keep all volumes consistent.
Oracle-defined Bronze, Silver, and Gold backup policies use incremental backups, cannot copy backups across regions, and are not supported for scheduled volume group backups.
Block Volume performance can be changed online: Lower Cost is 0 VPUs/GB, Balanced 10, Higher Performance 20, and Ultra High Performance 30–120.
Last updated: October 2026
Durability Inside the Availability Domain
The Block Volume service stores multiple copies of every block and boot volume on separate storage servers, with built-in repair. Oracle designs the service for 99.99% annual durability . That protects against disk and server failures, but not against losing the whole availability domain or region, so Oracle recommends regular backups and, for disaster recovery, replication to another location.
Block Volume Replication
Block Volume replication continuously and asynchronously copies block volumes, boot volumes, and volume groups to another location:
Cross-region replication copies data to a different region. Your tenancy must be subscribed to the destination region, and each source region has a list of allowed destination regions.
Cross-availability-domain replication copies data to another AD in the same region. It is only available in commercial regions that have more than one availability domain.
Important behaviors to remember:
Replication starts with an initial synchronization , which can take hours for large volumes. After that, replication is continuous.
Oracle's typical RPO target for cross-region replication is under 30 minutes , but the RPO is not guaranteed. Volumes with heavy write activity can lag by more than an hour.
Replication causes no downtime and no performance impact on the source volume.
You cannot resize a volume while replication is enabled. Resizing requires disabling replication, which deletes the replica, and then re-enabling it, which starts a new initial sync.
The replica is billed at the Lower Cost storage price, whatever the source performance level. Cross-region replication also incurs network transfer charges; cross-AD transfer is not billed.
Activating a Replica
A replica is not attached or used directly. To recover, you activate it. Activation creates a new volume (or a new volume group) by cloning the replica, and that new volume is what you attach to an instance in the recovery location. Replication into the replica continues for the source volume.
Volume Groups for Crash Consistency
Enterprise applications usually spread data across several volumes: a boot volume, data volumes, and log volumes. If each volume were copied on its own schedule, the copies could come from slightly different moments, and a database restored from them might be inconsistent.
A volume group solves this. It bundles boot and block volumes into one unit so that backups, clones, and replicas share a coordinated point in time:
Crash-consistent backups and clones : all member volumes are captured at the same moment, without stopping the instance.
Volume group replication : the whole group replicates to another region or AD. Oracle recommends activating the volume group replica , rather than individual volume replicas, so every volume is activated from the same synchronization point.
Full Stack Disaster Recovery depends on this. Moving compute instances in an FSDR protection group must have their boot and block volumes in a replicated volume group (or in volume group backups copied to the standby region).
Backup Policies
Backups complement replication. Replicas give you the current data; backups give you earlier points in time to recover from corruption, deletion, or ransomware.
Oracle-Defined Policies
Since November 3, 2021, the Oracle-defined policies contain incremental backups only . Their schedules and retention cannot be changed:
- Policy Schedules (all incremental)
- Bronze Monthly on the 1st, kept 12 months; yearly in early January, kept 5 years
- Silver Bronze schedules plus weekly on Sunday, kept 4 weeks
- Gold Silver schedules plus daily, kept 7 days
- User-Defined Policies
User-defined policies let you set your own frequencies (including hourly), retention periods, and full or incremental backup types. They are required in three common situations:
Automatic cross-region copy. Only user-defined policies can copy each scheduled backup to another region. If an Oracle-defined policy is close to what you need, duplicate it and enable cross-region copy on the copy. The copied backup keeps the same retention as the source backup.
Scheduled volume group backups. Oracle-defined policies are not supported for scheduled volume group backups.
Compliance scenarios that require scheduled full backups.
Vault keys are not copied with cross-region backup copies. If you use customer-managed encryption keys, you specify a key in the destination region when you assign the policy.
Performance Levels and Online Changes
Block Volume performance is purchased as volume performance units (VPUs) per GB . You can change the level of an attached volume online, without detaching it or restarting the instance.
- Performance level VPUs/GB IOPS/GB Max IOPS per volume Max MB/s per volume Notes
- Lower Cost 0 2 3,000 480 Block volumes only, not boot volumes
- Balanced (default) 10 60 25,000 480 Default for block and boot volumes
- Higher Performance 20 75 50,000 680 High-I/O databases
- Ultra High Performance 30–120 90–225 up to 300,000 up to 2,680 Requires multipath-enabled attachments
From Balanced upward, each additional 10 VPUs/GB adds 15 IOPS/GB, following the formula IOPS/GB = 1.5 × VPUs/GB + 45. Size matters too: a Balanced volume reaches its 25,000 IOPS maximum at about 417 GB.
Putting It Together
A typical cross-region design for a stateful compute tier combines a volume group (consistency), cross-region volume group replication (low RPO), and a user-defined backup policy with cross-region copy (point-in-time recovery). Full Stack DR then orchestrates activation of the replica and the launch of compute instances in the standby region.