Loading...

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

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:

 

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: Azure’s Upcoming Feature for Region Flexibility

 

If the customer prefers to avoid third-party solutions, there is good news. Although Azure Backup currently restricts Cross-Region Restore to paired regions, the Azure Product Group (PG) is actively working on a new feature that will allow customers to replicate backup data between any two regions of their choice. This feature is expected to enter preview by Q1 CY2025.

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:

 

Published on:

Learn more
Azure Migration and Modernization Blog articles
Azure Migration and Modernization Blog articles

Azure Migration and Modernization Blog articles

Share post:

Related posts

Azure AI Agents are in the Public Preview

AI agents are becoming a key enabler for businesses looking to streamline processes, automate repetitive tasks, and empower their employees to...

3 hours ago

Simplify your .NET data transfers with the new Azure Storage Data Movement library

This post announces the new and improved Azure Storage Data Movement library for .NET. The post Simplify your .NET data transfers with the new...

6 hours ago

External REST Endpoint Invocation in Azure SQL Managed Instance is now in Public Preview

External REST Endpoint Invocation is available in Azure SQL Managed Instance with the Always-up-to-date update policy configured. Call Azure S...

8 hours ago

Announcing the end of support for Node.js 18.x in the Azure SDK for JavaScript

After July 10, 2025, the Azure SDK for JavaScript will no longer support Node.js 18.x. Upgrade to an Active Node.js Long Term Support (LTS) ve...

1 day ago

February Patches for Azure DevOps Server

Today we are releasing patches that impact our self-hosted product, Azure DevOps Server. We strongly encourage and recommend that all customer...

1 day ago

Primer: Using Exchange Online PowerShell in Azure Automation Runbooks

In this primer, we cover how to create and execute Azure Automation Exchange Online runbooks (scripts) using cmdlets from the Exchange Online ...

2 days ago

Azure Developer CLI (azd) – February 2025

This post announces the February release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) – February 2025 appeared...

5 days ago

Using Azure AI Foundry SDK for your AI apps and agents

Design, customize and manage your own custom applications with Azure AI Foundry right from your code. With Azure AI Foundry, leverage over 1,8...

5 days ago

Azure Data Studio Retirement

We’re announcing the upcoming retirement of Azure Data Studio (ADS) on February 6, 2025, as we focus on delivering a modern, streamlined SQL d...

6 days ago

Microsoft Copilot (Microsoft 365): Developers building agents in Azure AI Foundry can ground their agent in files stored in SharePoint

Tenant Graph grounding provides grounding for agents with relevant information from Microsoft Graph, including files stored in SharePoint. Thi...

6 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy