Add a Non-Moving Instance to a Disaster Recovery Protection Group
Learn how to add a non-moving Instance to a Disaster Recovery (DR) Protection Group.
- From the Resource Type menu, Select Compute.
- If prompted, accept the warning that adding or removing members requires you to refresh and verify all the existing plans in the protection group.
Note
Ensure to add the resources only to the primary DR Protection group. - Select the instance to add from the list of instances.
- Select the card for a Non-moving instance.
Non-Moving Instance
A non-moving instance is not moved from a DR Protection Group to its peer DR Protection Group during DR operations. You use non-moving instances in Active-Passive DR topologies where instances which comprise the application stack are pre-deployed in both regions and application software components. You start or stop these instances during DR operations in order to transition the service from one region to another.
The instances always stay in the region where you deploy them and do not transition from one DR Protection Group to another.
When you add an instance, a non-moving instance is added to the DR Protection Group. No additional member properties (configuration information) are required.
Provide the following configuration information:
In the Show advanced options, for a new non moving instance, the following options are available:
- In Settings, you can select Start and stop instance on failover/switchover.
- In Block volumes enter the following information:
- Block volume in compartment: Select a compute instance.
Note
If the compute instance is a member of primary DR Protection Group, then select the block volume which is attached to that compute instance. If the compute instance is a member of the standby DR Protection Group, then select the block volume from the primary region. - (Optional) Volume attachment reference instance in compartment: Volume attachment reference is the peer compute instance used to get the attachment details.
Note
The value of the reference compute instance should always be from the peer region irrespective of the region (primary or standby). - Select the + Another block volume mapping to add other block volumes.
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.Note
Ensure to configure the block volumes on both the standby and the primary region for a switchover plan. - (Optional) Mount point: The physical mount point used for mounting and unmounting.
- Select the + Another mount point to add other mount points.
- Block volume in compartment: Select a compute instance.
- In File systems enter the following information:
- Export path: Export path for the file system. Example: </fs-export-path>
- Mount point: Physical mount point for the file system. Example: </mnt/yourmountpoint>
- Target in compartment: Select the mount target which is used to unmount on primary DRPG member and is then used to mount on the standby DRPG Member.
- Select the + Another export mapping to add other file system.
- Click Add to add the compute instance to the DR Protection Group.
Related Topics