Azure Site Recovery overview (preview)
Azure Site Recovery on Azure Stack Hub helps ensure business continuity by keeping business apps and workloads running during outages. Azure Site Recovery on Azure Stack Hub replicates virtual machine (VM) workloads 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.
During the public preview of Azure Site Recovery on Azure Stack Hub, updates might require a complete re-installation (a complete removal and then re-add) of the service.
To enable replication of VMs across two Azure Stack Hub stamps, configure the following environments:
Source environment is the Azure Stack Hub stamp where tenant VMs are running.
- Azure Stack Hub Operator, download the Azure Site Recovery Appliance VM and the Azure Site Recovery VM extensions in the Marketplace Management.
- Azure Stack Users, in the user subscriptions, configure the connection to the target vault in this source environment.
Target environment is where the Azure Site Recovery Resource Provider and dependencies run.
Azure Site Recovery on Azure Stack Hub is available for both Microsoft Entra ID and Active Directory Federation Services (AD FS) type deployments of Azure Stack Hub, which means it can run in disconnected environments.
What does Site Recovery provide?
Azure Site Recovery provides many features, as described in the following table.
|Using Site Recovery, you can set up and manage replication, failover, and failback from a single location in the Azure Stack Hub portal.
|Site Recovery integrates with other BCDR technologies. For example, you can use Site Recovery to protect the SQL Server backend of corporate workloads, with native support for SQL Server Always On, to manage the failover of availability groups.
|Azure Automation integration
|A rich Azure Automation library provides production-ready, application-specific scripts that can be downloaded and integrated with Site Recovery.
|RTO and PRO targets
|Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits. Site Recovery provides continuous replication for Azure Stack Hub VMs.
|Keep apps consistent over failover
|You can replicate using recovery points with application-consistent snapshots. These snapshots capture disk data, all data in memory, and all transactions in process.
|Testing without disruption
|You can easily run disaster recovery drills, without affecting ongoing replication.
|You can run planned failovers for expected outages with zero-data loss or unplanned failovers with minimal data loss, depending on replication frequency, for unexpected disasters. You can easily fail back to your primary site when it's available again.
|Customized recovery plans
|Not currently available in public preview. Using recovery plans, you can customize and sequence the failover and recovery of multi-tier applications running on multiple VMs. You can group machines together in a recovery plan, and optionally add scripts and manual actions.
What can I replicate?
Azure Site Recovery on Azure Stack Hub, with a required agent installed on each of the protected VMs, enables the replication of VMs across two instances, or stamps, of Azure Stack Hub. Azure Stack Hub uses a VM extension, available through the Azure Stack Hub Marketplace, to install this agent.
We've tested and validated the following VM OSs and each has respective Azure Stack Hub Marketplace images available for download:
|Windows Server 2022
|Windows Server 2019
|Supported for Server Core, Server with Desktop Experience.
|Windows Server 2016
|Supported Server Core, Server with Desktop Experience.
|Windows Server 2012 R2
|Windows Server 2012
|Windows Server 2008 R2 with SP1/SP2
|Supported. From version 9.30 of the Mobility service extension for Azure VMs, you need to install a Windows servicing stack update (SSU) and SHA-2 update on machines running Windows Server 2008 R2 SP1/SP2. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install or upgrade as expected. For more information, see SHA-2 upgrade and requirements.
|Windows 10 (x64)
|Windows 8.1 (x64)
|Windows 8 (x64)
|Windows 7 (x64) with SP1 onwards
|Supported. From version 9.30 of the mobility service extension for Azure VMs, install a Windows servicing stack update (SSU) and SHA-2 update on machines running Windows 7 with SP1. From September 2019, SHA-1 isn't supported, and if SHA-2 code signing isn't enabled the agent extension won't install or upgrade as expected. For more information, see SHA-2 upgrade and requirements.