Azure Site Recovery || Azure Disaster Recovery

Azure Site Recovery || Azure Disaster Recovery

What is Azure Site Recovery?

With this disaster recovery setup, Azure VMs continuously replicate to a different target region. If an outage occurs, VMs will failover to the secondary region, and can be accessed there. When everything is running normally again, resources will fail back and continue working in the primary location. Routing user traffic from primary region to secondary region during a disaster and then back to primary region once it is up again will be handled by Azure Traffic Manager.

Azure Disaster Recovery (DR) Resources:

  • Network Components
  • Shared Image Gallery
  • Automation account
  • Azure Active Directory
  • Custom RBAC Roles
  • Cloud security components
  • Azure Key Vault
  • Azure Event Hub
  • Storage Account
  • Recovery Services Vault
  • Log Analytics Workspace

Azure Disaster Recovery (DR):

This Section presents an overview of disaster recovery (DR) design, decision tree and architecture. DR design solution is derived using the decision tree outputs and various considerations, which will help customer to manage the DR solution. Disaster recovery will help customer to keep running and supporting the business—even during major IT outages.

Acceptable deployment strategies to support disaster recovery may vary based on the Recovery Time Objective and Recovery Point Objective requirements for each SAP workload. Depending on the Cloud Foundation Build and Disaster Recovery RTO and RPO requirements some of the above resources might not be required or some additional resources might be required. For the databases, Customer will go for Asynchronous replication between Primary and Secondary region. Depending on RTO requirements of SAP workloads, application layer would be recovered using one of the two methods below:

Azure Site Recovery RTO:

The Recovery Time Objective (RTO) is the duration of time within which a business process must be restored after a disaster to avoid unacceptable consequences associated with a break in continuity. Depending on RTO requirements, <<Customer>> will choose to restore SAP workloads in DR region either by building from scratch or replication using Azure Site Recovery. 

Azure Site Recovery RPO:

The Recovery Point Objective (RPO) describes the interval of time that might pass during a disruption before the quantity of data lost during that period exceeds the Business Continuity Plan’s maximum allowable threshold or tolerance. Depending on RPO requirements, Customer will choose to have synchronous or asynchronous replication of databases between primary and secondary regions.

Azure resources pre-built for any DR scenario. There are several Azure resources which will be pre-built in DR Azure region. Pre-building these resources mentioned below will ensure that bare minimum cloud platform build is in place for any DR scenario. Most of these resources have no or minimal cost attached with creation of the same.

Azure Site Recovery: Replication and Orchestration

Azure Site Recovery is simply known as ASR. Azure Site Recovery is a one way to achieve Business Continuity and Disaster Recovery (BCDR). Site Recovery is heterogeneous and can secure Hyper-V, VMware, and physical servers. And it also continuously monitors the state and health of your protected instances.

ASR provides two types of functionalities such as Replication and Orchestration.

  • Replication handles synchronization of designated systems between the Primary site (PS) and a Secondary site (SS). ASR can perform replication for Hyper-V workloads on On-Premises and Virtual Machine Manager.
  • Orchestration handles failover and failback between the Primary site (PS) and a Secondary site (SS). ASR can perform orchestration for Hyper-V workload only.

Note: Secondary Site can be an on-premises data center or on Azure.

Azure Site Recovery Scenarios:

  • Migrate Azure VM between Azure Cloud Region
  • Hyper-V VM to Azure Cloud with Virtual Machine Manager (VMM)
  • Hyper-V VM to Secondary Site with Virtual Machine Manager (VMM)
  • Hyper-V to Azure Cloud without Virtual Machine Manager (VMM)
  • Hyper-V VM to Secondary Site using SAN Replication without Virtual Machine Manager (VMM)
  • Vmware/Physical to Azure Cloud
  • Vmware VM/Physical to Secondary Site (SS)
  • Migrate Amazon VM Instance to Azure Cloud
Checkout the page to know more about 👉 ASR supported regions