Add a Moving Instance to a Disaster Recovery Protection Group

Learn how to add a moving instance to a Disaster Recovery (DR) Protection Group.

Note:

Currently, you can only edit the existing members of the Compute resource type.

1. From the Resource Type menu, Select Compute.
2. Accept the warning that indicates that all DR Plans will be deleted.
3. Select the instance to add from the list of instances.
4. Select or deselect Move instance on switchover or failover based on your requirement.

Moving Instance

A moving instance is moved from a DR Protection Group to its peer DR Protection Group during DR operations.

Moving instances are typically used in Pilot Light DR topologies where instances which comprise the application stack are only deployed in the primary region. The instances are moved from the primary DR Protection Group to the standby DR Protection Group.

When you add a moving instance to a DR Protection Group, provide the following configuration information:

• Click Add VNIC mapping. For each of the instance's VNICs, provide a VNIC to destination subnet mapping that indicates the subnet in the destination (standby) region to which the VNIC will attach after the instance moves to the destination (standby) region. Provide the following details:
  • VNIC
  • Destination subnet in your compartment
  • (Optional) Destination primary private IP address: Assign a value for the primary private IP address.

    Note:

    If you provide the IP address in one of the moving compute instances, then ensure to add the IP address for the other compute instances as well.

    Note:

    For a moving instance, you can choose to reassign the same private IP address and hostname to an instance that is relocated during disaster recovery.
  • (Optional) Destination primary private IP hostname label: Assign a value for the primary private IP hostname label.
  • Network Security Groups: You can select the Destination network security group in your compartment and also add another network security groups.
• If the VNIC has a public IP address in the source subnet, the selected destination must support public IP addresses. Else, the VNIC mapping is treated as a configuration error. OCI Networking assigns an appropriate public IP address in the selected destination subnet. You cannot select public IP addresses.

• The rules for assigning primary and secondary private IP addresses of a VNIC in the destination region are:

  • If the CIDR block for the VNIC's source subnet matches the CIDR block for the VNIC's destination subnet, and the private IP address is available in the destination subnet, then the Full Stack DR assigns the same private IP address. Else, Full Stack DR assigns another available private IP address.

  • If the CIDR block for the VNIC's source subnet does not match the CIDR block for the VNIC's destination subnet, then Full Stack DR assigns another available private IP address in the destination subnet.

    Note:

    You must provide VNIC mapping information for all VNICs that you have configured for an instance. If you do not provide VNIC mapping information, you will receive errors when you create DR Plans for disaster recovery.

• The rules for assigning host names are:

  • If the host name assigned to a VNIC is available in the destination subnet, that same host name is assigned.

  • If the host name assigned to a VNIC is not available in the destination subnet, another host name is assigned.

    Note:

    Assigning host names only applies to the short host name. The long (fully qualified) host name is determined the by the destination subnet and its VCN.
  • (Optional) Provide one or more network security groups that you want to assign to the VNIC in the destination region.

In the Show advanced options, for a new movable instance, following options are available:

• In Settings, you can select Retain fault domain. When you check this box, the newly created compute instances are launched in the same fault domains as of the primary region. If you reserve any capacity on the standby region, ensure that the capacity reserved on the standby region is specific to that fault domain as the instance is launched in the same fault domain.
  • Example 1: If the primary region is on faultdomain-1, then the standby region must be in faultdomain-1. If you do not check this box, then there should be some capacity reservation on the standby region which is not specific to the fault domain. Consequently, the First available fault domain is used for capacity reservation.
  • Example 2: If there is some capacity reservation on the standby region for faultdomain-2 and if you do not retain the fault domain, then the switchover fails during precheck.

• In Destination, select any of the following configurations:
  • (Optional). Select Destination compartment to provide a compartment in the destination (standby) region to which you want to move the compute instance. If you do not provide a destination compartment, the instance moves to the same compartment in which it resides in the primary region.
  • (Optional). Default destination This option is checked by default.
  • (Optional). Select a pre-provisioned Destination dedicated VM host in the destination region where you want to launch the instance. If you do not select a dedicated VM host, then the instance will launch using standard OCI provisioning procedures for new instances.

  Note:

  It is not common to launch instances on dedicated VM hosts, unless those instances have specific hardware or capacity requirements.
  • (Optional). Select a pre-provisioned Destination capacity reservation in the destination region where you want to launch the instance. If you do not select a capacity reservation, then the instance will launch using standard OCI provisioning procedures for new instances.
  • (Optional). Select a pre-created Destination capacity reservation in compartment from the standby region. Use the Compartment list in the panel on the left to change the compartment. This ensures that the reserved capacity is used when the instance is created. If you do not select a reservation ID, then the instance will be created using on-demand capacity. Reserve the capacity on the standby region so that when you move the movable instance to the standby region, the pre-reserved capacity is used. See Capacity Reservations for more information.

    Note:

    The Destination dedicated VM host and Destination capacity reservation are mutually exclusive, only one can be provided for an instance member. The rules for assigning a destination capacity reservation ID are as follows:

    • The capacity reservation ID can be given only for moving instances.
    • The capacity reservation must be pre-created and must be in an active state.
    • The availability domain of the given capacity reservation must match the destination availability domain where you want to move the instance. Generally the availability domain is where you replicate the boot volume.
    • The destination capacity reservation can be included only if the destination dedicated VM host is excluded.
    • The provided capacity reservation must have a capacity configuration entry matching that of the compute instance's shape configuration (instanceShape, memoryInGBs, ocpus)
• In the File systems tab, 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>
  • Unmount target in compartment: Select the unmount target.
  • Mount target in compartment: Select the mount target.
  • Select the + Another export mapping to add other file system.

• Click Add to add the compute instance to the DR Protection Group.