Loading...

Announcing the Public Preview of Azure Site Recovery with Azure Stack HCI

Announcing the Public Preview of Azure Site Recovery with Azure Stack HCI

In October 2021 we announced the support of Azure Site Recovery to protect virtual machines (VM) workloads on Azure Stack HCI. Based on customer feedback, we have improved the ASR agent deployment experience and now we are excited to announce the Public Preview of the new ASR agent deployment experience as an Arc extension. 

 

What is Azure Site Recovery (ASR)?

ASR is an Azure service that helps ensure business continuity by keeping business apps and workloads running during outages. ASR replicates workloads running on physical and virtual machines from a primary site to a secondary location. When an outage occurs at your primary site, you fail over to a secondary location, and access apps from there. After the primary location is running again, you can fail back to it.

Shijo_Joy_0-1684306636314.png

In case of an outage, you can failover your VM workloads from Azure Stack HCI to Azure and access your VMs on Azure. Once your Azure Stack HCI cluster is running again, you can failback the VM workloads to your Azure Stack HCI cluster. 

 

What's new in Public Preview?

The ASR agent is now packaged as an Arc extension. From the Azure portal, you can deploy the ASR agent to the nodes of your Azure Stack HCI cluster as an Arc extension. If a node is added at a later point in time, the ASR agent will be automatically deployed to the newly added node, by virtue of it being an Arc extension. This reduces the overhead of needing to install the agent manually on every cluster node and simplifies the steps to prepare the infrastructure prior to protecting your VM workloads. Once the extension is installed, you can leverage the existing ASR flow to protect, failover and failback VMs. 

 

There are a few prerequisites to deploy the ASR agent as an Arc extension to the nodes of your Azure Stack HCI cluster:

  • Azure Stack HCI cluster should be registered with Azure and Arc-enabled. If you registered your cluster on or after June 15, 2021, this happens by default. Otherwise, you'll need to enable Azure Arc integration.  
  • The cluster must have Azure Stack HCI version 22H2 and the May 2023 cumulative update or later installed.  
  • Enable managed identity on your Azure Stack HCI resource.

We've added a new "disaster recovery" item within the Azure Stack HCI resource on the Azure portal. 

 

Shijo_Joy_1-1684317778602.png

 

Selecting "Protect VM workloads" will take you to a two-card layout where you can select "Prepare infrastructure". 

 

Shijo_Joy_3-1684318046078.png

You can configure the vault, site and replication policy, right within the Azure Stack HCI resource without navigating elsewhere within the Azure portal. The agents will then get deployed to the nodes of the HCI cluster as an Arc extension. Try it out for yourself!

 

Shijo_Joy_5-1684318146645.png

 

If you have any feedback, send it to [email protected].

 

Learn more about how you can use Azure Site Recovery to protect your VM workloads on Azure Stack HCI

 

 

 

 

Published on:

Learn more
Azure Stack Blog articles
Azure Stack Blog articles

Azure Stack Blog articles

Share post:

Related posts

Effortless Scaling: Autoscale goes GA on vCore-based Azure Cosmos DB for MongoDB

We’re thrilled to announce that Autoscale is now generally available (GA) for vCore-based Azure Cosmos DB for MongoDB! Say goodbye to manual s...

2 hours ago

Making MongoDB workloads more affordable with M10/M20 tiers in vCore-based Azure Cosmos DB

vCore based Azure Cosmos DB for MongoDB is expanding its offerings with the new cost-effective M10 and M20 tiers for vCore-based deployments. ...

5 hours ago

Replacing jackson-databind with azure-json and azure-xml

This blog post explains how azure-json and azure-xml replaced jackson-databind in the Azure SDK for Java. The post Replacing jackson-databind ...

20 hours ago

March 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...

22 hours ago

Implementing Chat History for AI Applications Using Azure Cosmos DB Go SDK

This blog post covers how to build a chat history implementation using Azure Cosmos DB for NoSQL Go SDK and langchaingo. If you are new to the...

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