# Performing a Failback for a Periodic Replication Group

After a successful replication group failover, you can perform a failback operation to reestablish replication operations for all replication pairs in the group. Only eligible VMs will fail back. During a failback operation, all changes to the destination VMs are synced back to the source VMs. OpenStack failback uses incremental backups to efficiently synchronize data changes during this process.

Hyper-V failback is only supported on hosts running Windows Server 2016 or above.

Note

- After failover, if network changes are made to the destination VM, the failback job completes. The source VM will not reflect the network changes.

- After failover of VMware source VMs and reverse replication of VMware destination VMs, failback operation supports disk expansion on the destination VMs and syncs to the source VMs.

- Disk expansion and disk addition are supported for the following replication pairs.

  - Amazon Web Services to Amazon Web Services

  - Azure to Azure

  - Google Cloud to Google Cloud

  - VMware to VMware

  - VMware to Azure / Amazon Web Services / Google Cloud

## Procedure

1. From the Command Center navigation pane, go to Secure > Auto recovery > Replication groups.

   The Replication groups page appears.

2. Under Group name, click a replication group.

   The Overview tab of the replication group page appears.

3. In the upper-right area of the page, click Failover, and then select Failback.

   A message appears that asks you to verify that you want to perform the failback.

4. If you want to discard any changes that were made to the backup VM before the failback operation, select Discard the changes since failover.

   If you select this option, the failback operation becomes an undo failover operation.

5. Click Failback.

## Results

- The destination VMs are turned off.

- An incremental backup job runs on the destination VMs.

  Note

  - After performing a planned failover for VMware, the failback backup and replication process will be incremental. But, for unplanned failover, the failback replication will be full.

  - For Hyper-V, Azure, and AWS, a full backup and replication is performed during the failback process.

- Any changes are restored to the source VMs.

- The source VMs are turned on.

- Sync resumes for the VMs.

×

Loading...