Taking over a resiliency group of virtual machines

Takeover is an activity initiated by a user when the production data center is down due to a natural calamity or other disaster, and the virtual machines need to be restored at the recovery data center to provide business continuity. The user starts the virtual machines at the recovery data center with the available data. Since it is an unplanned event, the data available at the recovery data center may not be up to date. You need to evaluate the tolerable limit of data loss, and accordingly take the necessary action - start the virtual machines with the available data, or first use any other available data backup mechanism to get the latest copy of data, and thereafter start the virtual machines. The takeover operation brings up the virtual machines at the recovery data center using the last available data.

Perform the resync operation after successful completion of takeover operation.

If the recovery data center is in cloud, then takeover operation from cloud data center to production (on-premises) data center is not supported.

To perform takeover operation on virtual machines

  1. Prerequisites
    • It is recommended to stop or disable NetworkManager on RHEL hosts having multiple NICs.

    • For Hyper-V virtual machines, ensure that the network mapping of all the required virtual switches across the data centers is complete.

      See Setting up network mapping between production and recovery data centers.

    • If the recovery data center is in AWS, then ensure that the network mapping of all the required subnets between the production and recovery data center is complete.

  2. Navigate

    Assets (navigation pane)

    Resiliency Groups

  3. Double-click the resiliency group to view the details page. Click Takeover.
  4. Select the target data center and click Next.

If the Takeover operation fails, check Recent Activities to know the reason and fix it. You can then launch the Retry operation. The Retry operation restarts the migrate workflow, it skips the steps that were successfully completed and retries those that had failed.

Do not restart the workflow service while any workflow is in running state, otherwise the Retry operation may not work as expected.