Intro

Azure Site Recovery is a native disaster recovery as a service (DRaaS)

Documentation

• Azure Site Recovery

• About Site Recovery

• Azure to Azure disaster recovery architecture

• Set up disaster recovery of on-premises Hyper-V VMs to Azure

• Prepare Azure resources for Hyper-V disaster recovery

• Hyper-V VM Requirements For Migration

Tips and Tidbits

• Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location.

• When an outage occurs at your primary site, you fail over to secondary location, and access apps from there.

• Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits.

• Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V

• Site Recovery uses storage-based replication mechanism, without intercepting application data

• Azure Site Recovery also handles orchestration of failover and failback processes, which, to large extent, can be automated.

Site Recovery can manage replication for:

• Azure VMs replicating between Azure regions.

• On-premises VMs, Azure Stack VMs, and physical servers

• Azure Site Recovery provider:

  • Coordinates communications between on-premises servers and Azure

  • Hyper-V with Virtual Machine Manager: Installed on Virtual Machine Manager servers

  • Hyper-V without Virtual Machine Manager: Installed on Hyper-V hosts

• Replication happens on HTTPS channel, port 443 and an Azure egress cost is incurred for outbound traffic from the primary region.

• You can replicate on-premises VMs and physical servers to Azure, or to a secondary on-premises datacenter

• A Recovery Services vault is used to store data during backup and recovery activities.

  • If you intend to use the Recovery Services vault when you migrate a virtual machine between regions, you must ensure that the Recovery Services vault is created in any region except the region in which your virtual machine resides.

  • However, For you to create a vault to help protect any data source, the vault must be in the same region as the data source.

• Restrictions when migrating from on-prem to Azure: Hyper-V VM requirements, VMware VM Requirements

  • VM can’t have BitLocker enabled.

  • Hyper-V VM can’t have the OS disk larger than 2TB (gen 1) and 300GB (gen 2)

  • Hypver-V VM can’t have its data disk larger than 4TB

  • Linux Generation 2 VMs aren't supported.

Failover and Failback for Physical Servers

• Fail over and fail back physical servers replicated to Azure

  • fail over on-premises physical servers that are replicating to Azure with Azure Site Recovery.

• In Failover select a Recovery Point to fail over to. You can use one of the following options:

  • Latest: This option first processes all the data sent to Site Recovery. It provides the lowest RPO (Recovery Point Objective) because the Azure VM created after failover has all the data that was replicated to Site Recovery when the failover was triggered.

  • Latest processed: This option fails over the machine to the latest recovery point processed by Site Recovery. This option provides a low RTO (Recovery Time Objective), because no time is spent processing unprocessed data.

  • Latest app-consistent: This option fails over the machine to the latest app-consistent recovery point processed by Site Recovery.

  • Custom: Specify a recovery point.

Azure to Azure disaster recovery architecture

You need to configure outbound connectivity to allow virtual machines to be replicated from a source location to a target location. The process of configuring outbound connectivity will vary depending on whether you are using a URL-based firewall or a network security group to control traffic flow to and from your virtual machine. 

Open