Study guide
3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution
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
3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution
Key Takeaways Explain This Topic AI
Full Stack DR supports four plan types: Switchover, Failover, Start Drill, and Stop Drill.
Plan groups in a DR plan run sequentially, while all steps inside a single plan group run in parallel.
A switchover shuts down the application stack in the primary region before starting it in the standby region, so both regions must be available.
A failover brings up the application in the standby region without trying to shut down the primary, so it only needs the standby region to be available.
During an execution, operators can pause, resume, cancel, retry a failed step or group, or skip a step or group.
Last updated: October 2026
The Four Plan Types
All plans are created in the standby DR protection group, and all plan executions are launched from it.
Plan type When it is used What it does
Switchover Planned events: maintenance, DR audits, avoiding an approaching hazard Performs an orderly transition: shuts down the application stack in the primary region, then brings it up in the standby region. Requires both regions to be available.
Failover Unplanned outages that affect the primary region Immediately brings up the application stack in the standby region without trying to shut down the primary. Requires only the standby region.
Start Drill DR testing Creates a replica of the application stack in the standby region without disrupting production.
Stop Drill After testing Terminates the replica stack created by Start Drill and cleans up.
Data loss depends on the replication technology behind each member, not on Full Stack DR itself. A switchover performs graceful role changes, such as a Data Guard switchover, so no committed data is lost. A failover accepts whatever the replication lag was at the moment of failure; for example, a cross-region Autonomous Data Guard standby has an RPO of up to one minute.
How a Plan Is Structured
A DR plan is a sequence of plan groups , and each group contains plan steps :
Plan groups execute sequentially. Group 2 starts only after group 1 finishes.
All steps within a plan group execute in parallel. If ten moving instances must be launched, they launch at the same time inside one group.
Built-in groups and steps are generated automatically from the members. For a moving instance in a switchover plan, for example, Oracle generates groups such as Compute Instances - Stop (primary), Compute Instances - Launch (standby), Compute Instances - Terminate (disabled by default), and Compute Instances - Remove from DR Protection Group to prepare for switchback. Database members get groups such as Switchover Databases ; volume groups get groups that reverse or restore replication.
User-defined groups and steps are added after the plan is created. They can run a script stored in Object Storage , run a local script on an instance (through the Oracle Cloud Agent Run Command plugin), or invoke an OCI Function . You can also add a user-defined precheck and a pause group that stops the plan until an operator resumes it.
Each step has settings such as a timeout and an error mode . STOP_ON_ERROR halts the plan when the step fails so someone can fix the problem; CONTINUE_ON_ERROR records the failure and lets the plan continue, which suits optional tasks such as notifications.
If you move groups around manually or make large membership changes, the generated order can become wrong. Oracle documents a default order of DR plan groups and recommends checking it after edits, and refreshing plans when protection group members change.
Prechecks
A precheck validates that a plan still matches the members and configuration of the protection groups. Oracle positions prechecks as ongoing DR readiness checks that keep the workflow aligned with the topology it protects. You run them from the standby DRPG with Run Prechecks , and optionally choose Ignore Warnings :
With Ignore Warnings disabled, steps with warnings are marked Partially Succeeded .
With Ignore Warnings enabled, steps with warnings are marked Succeeded .
Examples of what Full Stack DR verifies include:
Member Example prechecks
Moving compute Volume group replication (or backups with cross-region copy) is configured; a replica or backup exists in the standby region; all boot and block volumes of the instance are in the volume group, and nothing else is
Volume groups Group and replica are Available; for intra-region DR, the replica is not in the same AD; destination encryption keys are valid and enabled
Base DB / Exadata databases Data Guard is enabled, the two databases are Data Guard peers with the correct roles, and the password secret in Vault can be read
Autonomous AI Database Serverless A remote (cross-region) standby exists, it belongs to the peer DRPG, and the primary is Available
Object Storage The source bucket and its replication policy exist in the peer region
Prechecks validate configuration. They do not reserve capacity, so a shape that is in short supply in the standby AD can still fail at launch time. For critical moving instances, compute capacity reservations in the standby region reduce that risk.
Running and Controlling an Execution
When an execution runs, the Console shows the progress of each group and step, with logs written to the Object Storage log location you configured for operation logs. Operators can:
Pause a running execution and Resume it later.
Cancel an execution.
Retry a failed step or a failed group after fixing the cause.
Skip a step or a group when it is safe to continue without it.
Full Stack DR can also be set up for automatic DR plan execution , with custom Audit events recorded for automatic runs. Most organizations still keep a human approval step for failover decisions.
Exam Patterns to Recognize
"Planned maintenance, both regions healthy, zero data loss, reverse roles afterward" points to a Switchover plan.
"Primary region unreachable" points to a Failover plan.
"Prove DR readiness without affecting production" points to Start Drill , followed by Stop Drill .
"Plans keep failing after members were added" points to refreshing the plan and rerunning prechecks.