Редагувати

Поділитися через

Tutorial: Fail back Azure VM to the primary region

  • Стаття

After failing over an Azure VM to a secondary Azure region, follow this tutorial to fail the VM to the primary Azure region, using Azure Site Recovery. In this article, you learn how to:

  • Review the prerequisites.
  • Fail back the VM in the secondary region.
  • Reprotect primary VMs back to the secondary region.

Note

This tutorial shows you how to fail back with minimal steps. If you want to run a failover with full settings, learn about Azure VM networking, automation, and troubleshooting.

Prerequisites

Before you start this tutorial, you should have:

  1. Set up replication for at least one Azure VM, and tried out a disaster recovery drill for it.
  2. Failed over the VM from the primary region to a secondary region, and reprotected it so that it replicates from the secondary region to the primary.
  3. Check that the primary region is available, and that you're able to create and access new resources in it.

Fail back to the primary region

After VMs are reprotected, you can fail back to the primary region as needed.

  1. In the vault > Replicated items, select the VM.

  2. On the VM overview page, check that the VM is healthy, and that synchronization is complete, before you run a failover. The VM should be in a Protected state.

    VM overview page showing VM in a protected state

  3. On the overview page, select Failover. Since we're not doing a test failover this time, we're prompted to verify.

    Page showing we agree to run failover without a test failover

  4. In Failover, note the direction from secondary to primary, and select a recovery point. The Azure VM in the target (primary region) is created using data from this point.

    • Latest processed: Uses the latest recovery point processed by Site Recovery. The time stamp is shown. No time is spent processing data, so it provides a low recovery time objective (RTO).
    • Latest: Processes all the data sent to Site Recovery, to create a recovery point for each VM before failing over to it. Provides the lowest recovery point objective (RPO), because all data is replicated to Site Recovery when the failover is triggered.
    • Latest app-consistent: This option fails over VMs to the latest app-consistent recovery point. The time stamp is shown.
    • Custom: Fail over to particular recovery point. Custom is only available when you fail over a single VM, and don't use a recovery plan.

    Note

    If you fail over a VM to which you added a disk after you enabled replication for the VM, replication points will show the disks available for recovery. For example, a replication point that was created before you added a second disk will show as "1 of 2 disks".

  5. Select Shut down machine before beginning failover if you want Site Recovery to attempt to shut down the source VMs before starting failover. Shutdown helps to ensure no data loss. Failover continues even if shutdown fails.

    Failover settings page

  6. To start the failover, select OK.

  7. Monitor the failover in notifications.

    Notification for failover progress
    Notification for failover success

Reprotect VMs

After failing back VMs to the primary region, you need to reprotect them, so that they start replicating to the secondary region again.

  1. In the Overview page for the VM, select Re-protect.

    Button to reprotect from the primary region

  2. Review the target settings for the primary region. Resources marked as new are created by Site Recovery as part of the reprotect operation.

  3. Select OK to start the reprotect process. The process sends initial data to the target location, and then replicates delta information for the VMs to the target.

    Page showing replication settings

  4. Monitor reprotect progress in notifications.

    Reprotect start notification Reprotect finish notification

Clean up resources

For VMs with managed disks, after failback is complete and VMs are reprotected for replication from primary to secondary, Site Recovery automatically cleans up machines in the secondary disaster recovery region. You don't need to manually delete VMs and NICs in the secondary region. VMs with unmanaged disks aren't cleaned up.

If you completely disable replication after failing back, Site Recovery cleans up machines protected by it. In this case, it also cleans up disks for VMs that don't use managed disks.

Next steps

In this tutorial, you failed VMs back from the secondary region to the primary. This is the last step in the process that includes enabling replication for a VM, trying out a disaster recovery drill, failing over from the primary region to the secondary, and finally failing back.

Now, try out disaster recovery to Azure for an on-premises VM.