Note:
- This tutorial requires access to Oracle Cloud. To sign up for a free account, see Get started with Oracle Cloud Infrastructure Free Tier.
- It uses example values for Oracle Cloud Infrastructure credentials, tenancy, and compartments. When completing your lab, substitute these values with ones specific to your cloud environment.
Enable Block Storage Logical Volume Manager Support in OCI Full Stack Disaster Recovery
Introduction
Oracle Cloud Infrastructure Full Stack Disaster Recovery (OCI Full Stack DR) orchestrates the transition of compute, database, and applications between Oracle Cloud Infrastructure (OCI) regions from around the globe with a single click. Customers can automate the steps needed to recover one or more business systems without redesigning or re-architecting existing infrastructure, databases, or applications and without the need for specialized management or conversion servers.
Initial Deployment Architecture
-
1 x Non-moving compute on the primary region (
vmapp01
). -
1 x Non-moving compute on the standby region (
vmapp01dr
). -
1 x Volume group in primary region containing block volumes for
vmapp01
.
Note: Primary region is Frankfurt and standby region is London.
Objectives
Configure the newly introduced feature in OCI Full Stack DR that enables users to specify multiple mount points for a single block volume.
The following tasks will be covered in this tutorial.
- Task 1: Add instance vmapp01 to primary DR protection group.
- Task 2: Add volume group vgapp01 to primary DR protection group.
- Task 3: Add instance vmapp01dr to standby DR protection group.
- Task 4: Generate a Switchover Plan
- Task 5: Execute the Switchover Plan
- Task 6: Verify that the disks were mounted on the standby vm instance vmapp01dr
Prerequisites
-
This tutorial assumes that you have already created and associated the primary and standby DR Protection Groups. For more information on how to create DR protection groups see Manage Disaster Recovery Protection Groups
-
This tutorial assumes that the instance vmapp01 has block volumes attached and configured with logical volume manager (LVM), see Configure Logical Volumes on Oracle Linux
-
This tutorial assumes the reader has administrator privileges and the required Oracle Cloud Infrastructure Identity and Access Management (OCI IAM) policies for OCI Full Stack DR are already in place. For more information, see Configuring Identity and Access Management (IAM) policies to use Full Stack DR and Policies for Full Stack Disaster Recovery.
Task 1: Add instance vmapp01 to primary DR protection group.
-
In the primary DR protection group (
DRPG_BSS_LVM_FRA
), select Members and Add member. -
Add the compute VM (
vmapp01
) as a member.Note: You can now specify multiple mount points for a single block volume mounted by Full Stack DR. You can also specify multiple mount points for a logical volume (LV) which can consist of multiple block volumes. Attachments and mounts are now completely independent of each other.
Make sure that both primary and standby vm instances have the descriptive information about the filesystems.
Task 2: Add volume group vgapp01 to primary DR protection group.
-
In the primary DR protection group (
DRPG_BSS_LVM_FRA
), select Members and add the Volume Group (vgapp01
) as a member.
Task 3: Add instance vmapp01dr to standby DR protection group.
Repeat the same process indicated on the Task 1, but with the standby DR protection group DRPG_BSS_LVM_LON and the vm instance vmapp01dr.
Task 4: Generate a Switchover Plan
Switchover Plan: A type of DR plan that performs a planned transition of services from the primary DR protection group to the standby DR protection group.
-
Create a switchover plan in standby DR protection group
DRPG_BSS_LVM_LON
. -
Select Plans and click Create plan.
-
Enter the Name as
Switchover
and select the Plan type asSwitchover (planned)
. -
Click Create.
Task 5: Execute Switchover Plan in Standby DR protection group
Note:
The DR plans in the standby region should all be active at this point, which means OCI Full Stack DR can execute the active Failover, Switchover and DR Drill plans even if a catastrophic event causes an outage at the primary region. Switchovers are disruptive and require an outage. Therefore, this task can be performed at a later point in time when an outage can be scheduled to execute the switchover plan in the current standby region.
If you cannot complete this step now, do not forget to complete this task at some point in the future.
Execute the prechecks for the switchover plan you just created in the current standby region, then execute the switchover plan if the prechecks succeed.
Execute prechecks as an independent operation first as a best practice.
-
To begin, open the switchover plan in the standby region.
-
Click Run Prechecks.
-
A confirmation box will pop up. Click Run Prechecks in the confirmation box to continue.
Ensure the prechecks complete successfully as shown in the screenshot below. You may need to remediate any failed precheck steps at this point and then run the precheck again until all steps succeed.
Execute the Switchover plan.
-
To begin, click Execute plan.
-
A confirmation box will pop up. Click Execute plan in the confirmation box to continue.
-
Monitor the plan execution to ensure all steps in the plan succeed.
The following screenshot shows the successful completion of the switchover plan. However, you may encounter failed steps even though the prechecks completed successfully; there is a chance steps will fail as the recovery steps are being executed in reality. Remediate any failed steps and try again.
Task 6: Verify that the disks were mounted on the standby vm instance vmapp01dr
Connect to the standby VM instance vmapp01dr to display the information about total space and available space on a file system.
df -h
You can also list the Volume Groups created on the standby VM instance.
sudo vgs
Next Steps
There are two best practices that should be incorporated into the normal day-to-day operations to help ensure the readiness of your DR plans.
- Regular periodic execution of prechecks.
- Regular periodic execution of DR Drills.
Think about scheduling weekly prechecks of all DR plans in the standby DR Protection Group. Prechecks can be run at any time and have zero impact on production workloads. This will help ensure integrity of your DR plans, catching missing member resources, missing networks, the inability to find expected scripts called by user-defined steps, etc.
Another very important way of validating the readiness of your disaster recovery is to schedule periodic DR Drills once a month or quarter. DR Drills also have zero impact on production workloads, but give you the ability to validate recovery of compute, storage, Oracle databases and backend sets for load balancers in the standby region with the click of a single button. Learn more about Full Stack DR Drills.
Related Links
-
Oracle Cloud Infrastructure (OCI) Full Stack Disaster Recovery
-
Add a Non-Moving Instance to a Disaster Recovery Protection Group
-
Join #full-stack-dr slack channel
Acknowledgments
- Author - Raphael Teixeira (Principal member of technical staff for Full Stack DR engineering)
More Learning Resources
Explore other labs on docs.oracle.com/learn or access more free learning content on the Oracle Learning YouTube channel. Additionally, visit education.oracle.com/learning-explorer to become an Oracle Learning Explorer.
For product documentation, visit Oracle Help Center.
Enable Block Storage Logical Volume Manager Support in OCI Full Stack Disaster Recovery
G33634-01
Copyright ©2025, Oracle and/or its affiliates.