Performing a Planned Failover for a Continuous Replication Pair


You can perform a planned failover operation to switch to the destination site during maintenance on the source site. After a failover, you can perform a failback operation to return replication operations to the source site.

Before You Begin

Create a continuous replication group.

Note: You cannot customize IP address settings for VMs with encrypted disks. If you configure custom IP address settings for a replication group that includes VMs with encrypted disks, failover operations fail for those VMs.


  1. From the navigation pane, go to Disaster recovery > Replication Monitor.

    The Replication Monitor page appears.

  2. On the Continuous tab, in the row for the replication pair that you want to fail over, click the action button , and then select Planned failover.

    The Planned failover dialog box appears.

  3. From the Recover from list, select one of the following values:

    • Oldest point in time: Perform the failover from the oldest available recovery point of the destination VM.

      This is the only supported value for Live recovery because only one copy of the destination VM is maintained. Other values are available only for Granular recovery.

    • Latest recovery point: Perform the failover from the most recent recovery point.

  4. To restore to a specific host, select Override boot options, and then provide the following information:

    • For Destination host, enter the host name or click Browse to select an ESX host.

      Select an ESX server from a cluster that meets continuous replication requirements. The ESX server must have access to the same datastore as the VM selected for the planned failover operation.

    • From the Destination network list, select a network or Not Connected.

    • In Network settings and IP address settings, specify IP customization settings.

  5. Click Save.


  • The source VM is turned off.

  • Operations move to the destination VM.

  • If errors occur during a planned failover, the job fails and the source VM is powered off. You must power on the source VM manually, and then perform a resume operation.