Full Stack DR Built-in Plan Groups for DR Plans

OCI Full Stack DR supports the following member types and DR plans. When creating DR plans in the standby DR protection group, Full Stack DR automatically introspects the members added to the DR protection groups and generates built-in plan groups accordingly.

Resource types in DR protection group:

Following are the various types of resource that can be added as members to a DR protection group.

Table A-32 Resource types in DR protection group:

Resource type	Sub type
Compute	Moving instance Non-moving instance
Oracle Database	Autonomous container database Autonomous database Database Oracle Base Database Oracle Exadata on Oracle Public Cloud Oracle Exadata on Cloud@Customer Oracle Exadata on Exascale Infrastructure
Database	MySQL DB System PostgreSQL DB System
Storage	File System Volume group Object Storage bucket
Networking	Load Balancer Network Load Balancer
Developer services	OKE Cluster Oracle Integration Instance

DR plans:

Full Stack DR supports the following plan types.

Table A-33 DR plans

DR plans	Description
Switchover	Switchover DR plan performs a planned service transition from the primary to the standby DR Protection Group. It ensures an orderly transition by shutting down the application stack in the primary region before starting it in the standby region. This requires all the necessary application stack components and OCI services to be available in both regions.
Failover	Failover DR plan enables an unplanned, immediate service transition to the standby region by starting the application stack. It only requires the OCI services in the standby region and is used during primary region outages or disasters.
Start drill	Start DR Drill plan execution creates a replica of the application stack in the standby DR Protection Group. This replica allows for testing and validation of DR processes without impacting the primary environment.
Stop drill	Stop DR Drill plan execution terminates the application stack replica that was created by a Start DR Drill plan. This cleans up the standby environment after DR drill testing is complete.

Member topology in the DR protection groups:

Based on the application requirements, you can add various member types to the primary and standby DR protection groups. Inspect the expected members that you must add, based on the resource type and DR topology. This step is essential to ensure a seamless DR plan creation process and avoid errors.

Following are a few common guidelines:

If you add a moving instance (VM) to the primary DR protection group, you must also include the dependent volume group (boot and block volumes) in the same DR protection group.
If you add a non-moving instance (VM) to both the primary and standby DR protection groups:
- Replicate only the boot volumes for non-moving compute in a volume group that is a member of DR Protection Group.
- Optional: If you want Full Stack DR to detach one or more block volumes from a non-moving compute in primary region and automatically attach or mount the block volumes to a non-moving compute in the standby region, then replicate and include the dependent volume group (block volumes) only in the primary DR protection group.
For Oracle Database services, add the database with the primary role to the primary DR protection group and the database with the standby role to the standby DR protection group.
For MySQL DB system, add the primary database to the primary DR protection group and the standby database to the standby DR protection group.
For Load Balancers:
- Full Stack DR is not used to create or provision OCI load balancers.
- Load balancers must either exist or be provisioned using the OCI network service in both the primary and standby regions.
- Add the VMs that are included in backend sets for load balancers to the appropriate DR protection groups. Following are some of the guidelines:
  - Moving compute will only be members of the primary DR Protection Group.
  - Non-moving compute in primary region will only be members of the primary DR Protection Group.
  - Non-moving compute in standby region will only be members of the standby DR Protection Group.
For File Storage, add the primary file system to the primary DR protection group.
For Object Storage, add the primary bucket to the primary DR protection group.
For OKE clusters, add the primary OKE cluster to the primary DR protection group and the standby OKE cluster to the standby DR protection group.
If applications running in OKE clusters use persistent volumes such as block storage, file systems, or load balancers, then add these dependent resources to the respective DR protection groups based on the topology.
For Oracle Integration 3, you must enable the Oracle Managed Disaster Recovery option that is a feature of Oracle Integration 3 before it can be added to Full Stack Disaster Recovery; Oracle Integration service will automatically deploy instances in both regions.
For Oracle Integration 3, add the primary instance to the primary DR protection group and the secondary instance to the standby DR protection group.

Table A-34 Member topology in the DR protection groups

Resource type	Sub type	Primary DR protection group	Standby DR protection group	Comments
Compute	Moving instance	Add primary VM Add volume group ( boot and block volumes)	NA	Add compute and volume groups to the primary DR protection group. If you have dependent file systems requiring unmounting or mounting, configure these details in the File Systems tab within the advanced options. Ensure that the file systems are added to the primary DR protection group. For other advanced configurations such as default OCI placement, capacity reservations, and dedicated VM hosts, refer to the Full Stack DR documentation.
Compute	Non-moving instance	Add primary VM Add volume group (only block)	Add standby VM	Add compute resources to both protection groups. Add volume groups (block volume only )to the primary protection group. For block volumes requiring unmounting or mounting, configure these details in the Block volumes tab within the advanced options. The volume group containing these block volumes must be added to the primary DR protection group. For dependent file systems requiring unmounting or mounting, configure these details in the File Systems tab. To start or stop instances during failover/switchover, select the corresponding checkbox based on your requirements.
Oracle Database Autonomous database (ADB-S)	NA	Primary DB	Standby DB	Configure Data Guard using the OCI Console, CLI, or SDKs.
Oracle Database Autonomous container database (ADB-D and ADB-C@C)	NA	Primary DB	Standby DB	Configure Data Guard using the OCI Console, CLI, or SDKs.
Oracle Database BaseDB, ExaDB-D, ExaDB-C@C, ExaDB-XS	Oracle Base Database ( Base DB) Oracle Exadata on Oracle Public Cloud (ExaDB-D) Oracle Exadata on Cloud@Customer (ExaDB-C@C) Oracle Exadata on Exascale Infrastructure (ExaDB-XS)	Primary DB	Standby DB	Configure Data Guard using the OCI Console, CLI, or SDKs. During the addition of DB member, you need to enter the database `sys` password as a secret. Before entering this, ensure to create an OCI Vault and add the `sys` password as a secret. If you have manually configured Data Guard, then utilize the custom scripts and integrate them as part of user-defined plan groups.
Database - MySQL DB System	NA	Primary DB System	Standby DB system	Add MySQL DB systems to the respective DR protection groups and configure channel replication in the standby DB system between the Primary and standby DB systems.
Database - PostgreSQL DB System	NA	Primary DB System	Warm Standby DB system	Add PostgreSQL DB Systems to the respective DR protection groups and configure PostgreSQL replication between the primary and standby PostgreSQL DB Systems.
Storage - Volume group	NA	Volume group	NA	Add volume groups to the primary DR protection group. For moving instances, the volume group must include boot and block volumes. For non-moving instances, the volume group should contain only block volumes.
Storage- Object Storage bucket	NA	Primary Bucket	NA	Add the object storage bucket to the primary DR protection group.
Storage - File System	NA	File System	NA	Add the file systems to the primary DR protection group.
Networking - Network Load Balancer	NA	Primary load balancer	Standby load balancer	Add the dependent backend compute instances that are part of the LBR backend set to the respective protection group based on whether they are moving or non-moving instances.
Networking - Load Balancer	NA	Primary load balancer	Standby load balancer	Add the dependent backend compute instances that are part of the LBR backend set to the respective protection group based on whether they are moving or non-moving instances.
Developer Services- OKE Cluster	NA	Primary OKE	Standby OKE	Add the dependent databases and storage members to their respective protection groups if they are utilized within the OKE cluster.
Developer Services - Integration Instance	NA	Primary Integration Instance	Secondary Integration Instance	Configure Oracle Managed DR using the OCI Console, CLI or SDKs

Built-in plan groups for DR plans:

Based on DR plan types, several built-in plan groups are automatically created. Each plan group contains multiple sequential steps (plan steps), the number of which is determined by the number of members. Within each plan group, however, the plan steps execute in parallel.

Note:

The plan groups discussed here are specific to certain resource types, and ideally, your DR protection group would also include dependent members.

Compute

This functionality applies to OCI Virtual Machines and Dedicated Virtual Machine Hosts.

Table A-35 Compute

Resource type	Sub-type	Plan	Plan groups	Description
Compute	Moving	Switchover	Compute Instances - Stop	Stop compute instances in primary region
			Compute Instances - Launch	Launch compute instances in standby region
			Compute Instances - Terminate	Terminate compute instances in primary region. By default, this plan group is disabled, you can enable if required.
			Compute Instances - Remove from DR Protection Group	Add and remove compute instances from the DR protection group to facilitate the switchback process.
		Failover	Compute Instances - Launch	Launch compute instances in standby region
		Start Drill	Compute Instances - Launch	Launch compute instances in standby region
		Stop Drill	Compute Instances - Stop	Stop compute instances in standby region
			Compute Instances - Terminate	Terminate compute instances in standby region
			Compute Instances - Remove from DR Protection Group	Remove compute instances from the DR protection group
	Non-moving	Switchover	Detach block volumes from Compute instances	Detach block volumes from the compute instances in primary region
			Compute Instances - Stop	Stop compute instances in primary region
			Compute Instances - Start	Start compute instances in standby region
			Attach block volumes to Compute instances	Attach block volumes to he compute instances in standby region
		Failover	Compute Instances - Start	Start compute instances in standby region
		Failover	Attach block volumes to Compute instances	Attach block volumes to he compute instances in standby region
		Start Drill	Compute Instances - start	Start compute instances in standby region
		Start Drill	Attach block volumes to Compute instances	Attach block volumes to he compute instances in standby region
		Stop Drill	Detach block volumes from Compute instances	Detach block volumes from the compute instances in standby region
		Stop Drill	Compute Instances - Stop	Stop compute instances in standby region

Oracle Database - Autonomous Container database

This functionality applies to Oracle Autonomous Database on Dedicated Exadata Infrastructure (ADB-D) and Oracle Autonomous Database on Exadata Cloud@Customer (ADB-C@C).

Table A-36 Autonomous Container database

Resource type	Plan	Plan groups	Description
Autonomous Container database (ACD)	Switchover	Autonomous Container Databases - Switchover	Switchover the autonomous container database
	Failover	Autonomous Container Databases - Failover	Failover the autonomous container database
	Start drill	Autonomous Container Databases - Start Drill - Convert to Snapshot Standby	Convert the autonomous container database from physical standby to snapshot standby
	Stop drill	Autonomous Container Databases - Stop Drill - Convert to Physical Standby	Convert the autonomous container database from snapshot standby to physical standby

Oracle Database - Autonomous Database

This functionality applies to Oracle Autonomous Database Serverless (ADB-S) with the Autonomous Transaction Processing (ATP) workload type and Autonomous Data Warehouse (ADW) with cross-region Autonomous Data Guard (AuDG) enabled.

Table A-37 Autonomous Database

Resource type	Plan	Plan groups	Description
Autonomous database	Switchover	Autonomous Database - Switchover	Switchover the autonomous database
	Failover	Autonomous Database - Failover	Failover the autonomous database
	Start drill	Autonomous Database - Start drill - Convert to snapshot standby	Convert the autonomous database from physical standby to snapshot standby. This is applicable if you have selected Snapshot Standby while adding the member for DR drill
	Start drill	Autonomous Database - Start drill - Create clone	Create clone or refreshable clone in standby region. This is applicable you have selected Create clone or Refreshable clone while adding the member for DR drill
	Stop drill	Autonomous Database - Stop drill - Convert to physical standby	Convert the autonomous database from snapshot standby to physical standby. This is applicable If you have selected Snapshot Standby while adding the member for DR drill
	Stop drill	Autonomous Database - Stop drill - Delete clone	Delete/terminate clone or refereshable clone in standby region. This is applicable you have selected Create clone or Refreshable clone while adding the member for DR drill

Oracle Database

This functionality applies to: Oracle Base Database Service (Base DB), Oracle Exadata Database Service on Dedicated Infrastructure (ExaDB-D), Oracle Exadata Database Service on Cloud@Customer (ExaDB-C@C), and Oracle Exadata Database Service on Exascale Infrastructure (ExaDB-XS) with Data Guard set up across regions or availability domains.

Table A-38 Database

Resource type	Plan	Plan groups	Description
Database	Switchover	Database - Switchover	Switchover the Oracle database
	Failover	Database - Failover	Failover the Oracle database
	Start drill	NA	This plan type is not currently supported for this resource. As a workaround,you can use custom scripts with user-defined plan groups. Note: This is applicable only for Base DB and ExaDB-XS.
	Stop drill	NA	This plan type is not currently supported for this resource. As a workaround,you can use custom scripts with user-defined plan groups. Note: This is applicable only for Base DB and ExaDB-XS.

Database - MySQL DB System

This functionality applies to: MySQL DB System

Table A-39 Database - MySQL DB System

Resource type	Plan	Plan groups	Description
MySQL DB System	Switchover	HeatWave MySQL DB System - Switchover	Switchover the MySQL DB System
	Failover	HeatWave MySQL DB System - Failover	Failover the MySQL DB System
	Start drill	HeatWave MySQL DB System - Start drill	Create clone of the MySQL DB system
	Stop drill	HeatWave MySQL DB System - Stop drill	Terminate clone of the MySQL DB system

Database - PostgreSQL DB System
This functionality applies to: PostgreSQL DB Systems configured with replication between primary and standby DB Systems across OCI regions

Table A-40 PostgreSQL DB System

Resource type	Plan	Plan groups	Description
PostgreSQL DB System	Switchover	OCI Database with PostgreSQL - Switchover	Switchover the PostgreSQL DB system
	Failover	OCI Database with PostgreSQL - Failover	Failover the PostgreSQL DB system
	Start drill	NA	NA
	Stop drill	NA	NA

Storage - Volume group

This functionality applies to setting up cross-region volume groups for boot and block volumes of block storage service.

Table A-41 Volume group

Resource type	Plan	Plan groups	Description
Volume group	Switchover	Volume Groups - Switchover	Switchover the volume groups in the standby region
		Volume Groups - Reverse Replication	Setup the reverse replication of the volume groups from the standby region
		Volume Groups - Terminate	Terminate the volume groups (stale) in the primary region. By default, this plan group is disabled, you can enable if required.
		Volume Groups - Remove from DR Protection Group	Add and remove volume groups from the DR protection groups to facilitate the switchback process
	Failover	Volume Groups - Failover - Restore	Restore the volume groups in the standby region
	Start Drill	Volume Groups - Start drill - Restore	Restore the volume groups in the standby region
	Stop Drill	Volume Groups - Terminate	Terminate the volume groups in the standby region
	Stop Drill	Volume Groups - Remove from DR Protection Group	Remove volume groups from the standby DR protection group

Storage - File System

This functionality applies to File Storage Service.

Table A-42 File System

Resource type	Plan	Plan groups	Description
File System	Switchover	File Systems - Unmount from Compute Instance	Unmount the file systems from the compute instance in the primary region
		File Systems - Switchover	Switchover the file systems in the standby region
		File Systems - Mount on Compute Instances	Mount the file systems from the compute instance in the standby region
		File Systems - Terminate	Terminate the file systems in the primary region. By default, this plan group is disabled, you can enable if required.
		File Systems - Reverse replicate	Setup the reverse replication for the file systems from the standby region
		File Systems - Remove from DR Protection Group	Add and remove file systems from the DR protection groups to facilitate the switchback process
	Failover	File Systems - Failover	Failover the file systems in the standby region
	Failover	File Systems - Mount on Compute Instances	Mount the file systems from the compute instance in the standby region
	Start Drill	File Systems - Restore for Start Drill	Restore the file systems in the standby region
	Start Drill	File Systems - Mount on Compute Instances	Mount the file systems from the compute instance in the standby region
	Stop Drill	File Systems - Unmount from Compute Instance	Unmount the file systems from the compute instance in the standby region
		File Systems - Terminate after stop drill	Terminate the file systems in the standby region
		File Systems - Remove from DR Protection Group	Remove file systems from the standby DR protection group

Storage - Object storage bucket

This functionality applies to Object storage bucket.

Table A-43 Object storage bucket

Resource type	Plan	Plan groups	Description
Object storage bucket	Switchover	Object Storage Bucket - Delete Replication (Primary)	Delete replication from the object storage buckets in the primary region
	Switchover	Object Storage Bucket - Setup Reverse Replication (Standby)	Setup reverse replication from the object storage buckets in the standby region
	Failover	Object Storage Bucket - Delete Replication (Standby)	Delete replication from the object storage buckets in the standby region
	Failover	Object Storage Bucket - Setup Reverse Replication (Standby)	Setup reverse replication from the object storage buckets in the standby region
	Start drill	NA	This plan type is currently not supported for this resource
	Stop drill	NA	This plan type is currently not supported for this resource

Networking - Load Balancer

This functionality applies to Application Load Balancer.

Table A-44 Load Balancer

Resource type	Plan	Plan groups	Description
Load Balancer	Switchover	Load balancer - Update source backend sets	Remove the backend servers from the backend sets in the primary region
	Switchover	Load balancer - Update destination backend sets	Add the backend servers from the backend sets in the standby region
	Failover	Load balancer - Update destination backend sets	Add the backend servers from the backend sets in the standby region
	Start drill	Load balancer - Update destination backend sets	Add the backend servers from the backend sets in the standby region
	Stop drill	Load balancer - Update destination backend sets	Remove the backend servers from the backend sets in the standby region

Networking - Network Load Balancer

This functionality applies to Network Load Balancer.

Table A-45 Network Load Balancer

Resource type	Plan	Plan groups	Description
Network Load Balancer	Switchover	Load balancer - Update source backend sets	Remove the backend servers from the backend sets in the primary region
	Switchover	Load balancer - Update destination backend sets	Add the backend servers from the backend sets in the standby region
	Failover	Load balancer - Update destination backend sets	Add the backend servers from the backend sets in the standby region
	Start drill	Load balancer - Update destination backend sets	Add the backend servers from the backend sets in the standby region
	Stop drill	Load balancer - Update destination backend sets	Remove the backend servers from the backend sets in the standby region

Developer Services - OKE Cluster

This functionality applies to Oracle Kubernetes Engine (OKE).

Table A-46 OKE Cluster

Resource type	Plan	Plan groups	Description
OKE Cluster	Switchover	OKE - Stop Backup and Cleanup (Primary)	Stop backup and cleanup resources from the OKE clusters in the primary region
		OKE - Restore (Standby)	Restore the resources in the OKE clusters in the standby region
		OKE - Schedule reverse backup (Standby)	Schedule reverse backup from the OKE clusters in the standby region
		OKE - Scale down (Primary)	Scale down the node pools of the OKE clusters in the primary region
		OKE - Scale up (Standby)	Scale up the node pools of the OKE clusters in the standby region
	Failover	OKE - Restore (Standby	Restore the resources in the OKE clusters in the standby region
	Failover	OKE - Scale up (Standby)	Scale up the node pools of the OKE clusters in the standby region
	Start Drill	OKE - Restore (Standby)	Restore the resources in the OKE clusters in the standby region
	Start Drill	OKE - Scale up (Standby)	Scale up the node pools of the OKE clusters in the standby region
	Stop Drill	OKE - Cleanup (Standby)	Cleanup resources from the OKE clusters in the standby region
	Stop Drill	OKE - Scale down (Standby)	Scale down the node pools of the OKE clusters in the standby region

Developer Services - Integration Instance

This functionality applies to Oracle Integration Cloud (OIC).

Table A-47 Oracle Integration Cloud (OIC)

Resource type	Plan	Plan groups	Description
Integration Instance	Switchover	Integration Instance - Switchover	Switchover the Integration instance
	Failover	Integration Instance - Failover	Failover the Integration instance
	Start Drill	NA	NA
	Stop Drill	NA	NA