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

GitHub Copilot for Azure: 6 Must-Try Features

As developers, we are constantly seeking tools that streamline our workflows and boost productivity. … Enter GitHub Copilot for Azure, now in ...

7 hours ago

Unlocking the Best of Azure with AzureRM and AzAPI Providers

With the recent release of AzAPI 2.0, Azure offers two powerful Terraform providers to meet your infrastructure needs: AzureRM and AzAPI. The ...

15 hours ago

Azure Communication Services Ideas Board: Share your feedback with the product team

Innovation is not a solitary pursuit, and we recognize that some of the best ideas come from you, our Azure Communication Services community. ...

16 hours ago

Engage with the Azure Community Services Ideas Board: Your Voice Matters

Innovation is not a solitary pursuit, and we recognize that some of the best ideas come from you, our Azure Communication Services community. ...

18 hours ago

Optimizing custom copilot (agent) performance with Azure Load Testing: A comprehensive guide

As we move into the next phase of digital transformation, the role of custom copilots is set to become increasingly pivotal. By leveragin...

19 hours ago

Azure Storage - TLS 1.0 and 1.1 retirement

Overview TLS 1.0 and 1.1 retirement on Azure Storage was previously announced for Nov 1st, 2024, and it was postponed recently to 1 year later...

23 hours ago

Streamline Your Azure Workflow: Introducing GitHub Copilot for Azure in VS Code

I'm excited to announce the public preview of GitHub Copilot for Azure - a new addition to your toolkit that seamlessly integrates with G...

1 day ago

VMware HCX Design with Azure VMware Solution

Overview VMware HCX is one of the Azure VMware Solution components that generates a large number of service requests from our customers. The A...

1 day ago

Efficient Management of Append and Page Blobs Using Azure Storage Actions

  Overview In Azure Storage, Blob Lifecycle Management (BLM) allows you to automate the management of your data based on rules defined by...

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