Welcome to the Azure Site Recovery service! This article provides a quick overview of the service.
Business continuity and disaster recovery (BDCR) with Azure Recovery Services
As an organization you need to figure out how you're going to keep your data safe, and apps/workloads running when planned and unplanned outages occur.
Azure Recovery Services contribute to your BCDR strategy:
- Site Recovery service: Site Recovery helps ensure business continuity by keeping your apps running on VMs and physical servers available if a site goes down. Site Recovery replicates workloads running on VMs and physical servers so that they remain available in a secondary location if the primary site isn't available. It recovers workloads to the primary site when it's up and running again.
- Backup service: In addition, the Azure Backup service keeps your data safe and recoverable by backing it up to Azure.
Site Recovery can manage replication for:
- Azure VMs replicating between Azure regions.
- On-premises virtual machines and physical servers replicating to Azure, or to a secondary site.
What does Site Recovery provide?
|Deploy a simple BCDR solution||Using Site Recovery, you can set up and manage replication, failover, and failback from a single location in the Azure portal.|
|Replicate Azure VMs||You can set up your BCDR strategy so that Azure VMs are replicated between Azure regions.|
|Replicate on-premises VMs offsite||You can replicate on-premises VMs and physical servers to Azure, or to a secondary on-premises location. Replication to Azure eliminates the cost and complexity of maintaining a secondary datacenter.|
|Replicate any workload||Replicate any workload running on supported Azure VMs, on-premises Hyper-V VMs, VMware VMs, and Windows/Linux physical servers.|
|Keep data resilient and secure||Site recovery orchestrates replication without intercepting application data. Replicated data is stored in Azure storage, with the resilience that provides. When failover occurs, Azure VMs are created based on the replicated data.|
|Meet RTOs and RPOs||Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organization limits. Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V. You can reduce recovery time objectives (RTO) further by integrating with Azure Traffic Manager integration.|
|Keep apps consistent over failover||You can configure recovery points with application-consistent snapshots. Application-consistent snapshots capture disk data, all data in memory, and all transactions in process.|
|Test without disruption||You can easily run test failovers to support disaster recovery drills, without affecting ongoing replication.|
|Run flexible failovers||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.|
|Create recovery plans||You can customize and sequence failover and recovery of multi-tier applications on multiple VMs with recovery plans. You group machines within plans, and add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.|
|Integrate with existing BCDR technologies||Site Recovery integrates with other BCDR technologies. For example, you can use Site Recovery to protect the SQL Server backend of corporate workloads, including native support for SQL Server AlwaysOn, to manage the failover of availability groups.|
|Integrate with the automation library||A rich Azure Automation library provides production-ready, application-specific scripts that can be downloaded and integrated with Site Recovery.|
|Manage network settings||Site Recovery integrates with Azure for simple application network management, including reserving IP addresses, configuring load-balancers, and integrating Azure Traffic Manager for efficient network switchovers.|
What can I replicate?
|What can I replicate?||Azure VMs between Azure regions (in preview)
On-premises VMware VMs, Hyper-V VMs, physical servers (Windows and Linux) to Azure
On-premises VMware VMs, Hyper-V VMs, physical servers to a secondary site. For Hyper-V VMs, replication to a secondary site is only supported if Hyper-V hosts are managed by System Center VMM.
|Which regions are supported for Site Recovery?||Supported regions|
|What operating systems do replicated machines need?||Azure VM requirementss
VMware VM requirements
For Hyper-V VMs, any guest OS supported by Azure and Hyper-V is supported.
Physical server requirements
|What VMware servers/hosts do I need?||VMware VMs can be located on supported vSphere hosts/vCenter servers|
|What workloads can I replicate?||You can replicate any workload running on a supported replication machine. In addition, the Site Recovery team have performed app-specific testing for a number of apps.|
Azure portal considerations
- Site Recovery can be deployed in the Azure portal.
- In the Azure classic portal, you can manage Site Recovery with the classic services management model.
- The classic portal should only be used to maintain existing Site Recovery deployments. You can't create new vaults in the classic portal.