Azure Backup and DR: Cross-Region Restore - Exploring Solutions

Azure Backup and DR: Cross-Region Restore - Exploring Solutions

When building a Disaster Recovery (DR) plan, customers often face challenges that require creative solutions, especially when capacity issues limit available options in Azure paired regions. In this article, we explore a real-world scenario and evaluate possible solutions for addressing Cross-Region Restore needs using Azure Backup.

Use Case

A customer wants to implement a DR plan based on the following requirements:

1. Host applications in a specific "XYZ" region.
2. For critical applications, establish a passive node in another region.
3. For less critical applications, utilize Cross-Region Restore functionality for VMs using Azure Backup.

Issue

The customer is facing capacity constraints in the paired Azure region associated with "XYZ." Consequently, they are exploring options to build DR in an alternate region outside the paired one.

Challenge

The key question is: Is there a way to redirect Azure Backup's Cross-Region Restore functionality to a region outside the default paired region? Or are there other solutions to restore a VM in a non-paired region?

Solution 1: Using Azure Site Recovery (ASR)

Based on Azure Backup documentation, VMs can only be restored to the original or its paired region. This creates a challenge if the paired region lacks the necessary capacity.

In this case, Azure Site Recovery (ASR) could be an alternative solution. For more information on Azure Site Recovery, refer to these resources:

• About Azure Site Recovery | Microsoft Learn
• Support Matrix for Azure VM Disaster Recovery with ASR | Microsoft Learn

However, the issue with this solution is that ASR is ideal for Azure Virtual Machines. The customer’s scenario involves SQL and PostgreSQL environments that require application-level consistency. ASR may not ensure the consistency needed for such databases, leading the customer to seek alternative solutions.

Solution 2: Leveraging Third-Party Solutions

Since Solution 1 does not fully meet the customer’s needs, an alternative approach is to use third-party backup solutions that allow copying backup data to a region of choice. Notable options include:

• Veeam
• Rubrik

For more detailed insights, check out Veeam vs. Rubrik: Why Veeam is the Better Choice.

Solution 3: Cross Region Restore 

If the customer prefers to avoid third-party solutions, there are other alternatives that can be tried. Although Azure Backup currently restricts Cross-Region Restore to paired regions, the Azure Product Group (PG) will be working on a new feature that will allow customers to replicate backup data between any two regions of their choice.

In the meantime, as a workaround, customers can use AzCopy to manually transfer backup data between regions. However, it’s important to note that this method is not supported for all workloads.

For more details, refer to:

• When to use AzCopy versus Azure PowerShell or Azure CLI | Microsoft Community Hub