Search This Blog

Wednesday, January 13, 2016

Azure Site Recovery (ASR) Use Case Scenario for Business Continuity and Disaster Recovery

[ Updated 13 January 2016 ]

Azure Site Recovery (ASR) provided by Microsoft allow you to replicate and migrate your workload from different scenario to Microsoft Azure or Secondary Data center site. Depend on your scenario, you can use ASR to perform DR orchestration such as failover, failback and test failover.

We have compiled and summarized ASR use case scenario into eight (8) with this simple guide.
Note:- Click an image file to view in large mode.

Scenario 1: Hyper-V VM (With VMM) to Azure


Virtual machine running on Hyper-V is replicate to Microsoft Azure and store in Azure Storage.
Requirements:-
  • VMM – VMM 2012 R2
  • Hyper-V – Windows Server 2012 R2

Must create private cloud using VMM
By using ASR, you can perform failover, failback & test failover

Asynchronous  replication frequency – 30 sec, 5 min, 15 min

For more detail, please refer to https://azure.microsoft.com/en-us/documentation/articles/site-recovery-vmm-to-azure/

Scenario 2: Hyper-V VM (With VMM) to Secondary Site


ASR provide DR orchestration . VMM metadata was sent to Microsoft Azure and customer has own secondary data center.
  • Must create private cloud using VMM.
  • By using ASR, you can perform failover, failback & test failover
  • Asynchronous  replication frequency – 30 sec, 5 min, 15 min
On both data center requirements:
  • VMM – min VMM 2012 SP1 with latest cumulative update
  • Hyper-V – min Windows Server 2012 with latest update

Scenario 3: Hyper-V to Azure (Without VMM)



Replicate Hyper-V Virtual Machine to Microsoft Azure without VMM
  • By using ASR, you can perform failover, failback & test failover
  • Asynchronous  replication frequency – 30 sec, 5 min, 15 min

Requirement:-
  • Hyper-V running Windows Server 2012 R2

Scenario 4: Hyper-V VM (With VMM) to Secondary Site Using SAN Replication



Provides disaster recovery (BCDR) strategy by orchestrating replication, failover and recovery of virtual machine by using SAN replication.

Supported SAN:
a)NetApp Clustered DATA ONTAP 8.2
b)HP 3PAR
c)EMC Vmwax Series
Refer to http://social.technet.microsoft.com/wiki/contents/articles/28317.deploying-azure-site-recovery-with-vmm-and-san-supported-storage-arrays.aspx

  • Must has SAN Replication license
  • Running VMM 2012 R2 with CU5
  • Integration with VMM using SMI-S Provider
  • Hyper-V Virtual Machine located in the SAN Storage
  • Require Secondary Datacenter with VMM, Hyper-V and SAN Storage


Scenario 5: Vmware/Physical to Azure


Latest enhancement for Vmware/Physical to Azure. You no longer require to deploy ASR component on Azure IaaS. Replication will direct to Azure Storage.


All traffic is encrypted & replication management using TCP 443
Limited support for Vmware vSphere 6

Management server requirements  (on-premise):
- 8 vcpu
- 16GB
- 600GB disk
- Win 2012 R2

Requirement on Vmware hypervisor:-
ESX/ESXi version 6.0, 5.5 or 5.1 with the latest updates
vCenter version 6.0 or 5.5 with the latest updates

Protected computerrequirement:-
Each disk not more than 1023 GB
Shared disk guest cluster is not supported
UEFI/EFI is not supported
RDP must enabled

Windows Workload supported:-
Supported from Windows Server 2008 R2 SP1, Win 2012, Win 2012 R2
Operating System installed on C:\ and use Windows basic disk

Linux workload supported:- 
-64 bit operating system
-SSH must enabled
-Red Hat Enterprise Linux 6.7; Centos 6.5, 6.6,6.7; Oracle Enterprise Linux 6.4, 6.5 SUSE Linux Enterprise Server 11 SP3


Scenario 6: Vmware VM/Physical to Secondary Site

ASR component install on Windows Server 2012 R2.

For linux workload, master target VM running Centos 6.4 or RHEL 6.4 (64 bit)

Primary Site should has Process Server (PS) VM
Secondary Site should has Master Target (MT) and Configuration Server (CS)

Supported Vmware hypervisor version:
- vCenter 5.1, 5.5
- vSphere ESX 5.1, 5.5 5.5U1, 5.5U2
- UEFI is supported by ESX 5.0 and later version only
- Windows 2012 is supported by ESX5.1 or later

Guest operating system supported (V2V):
- Windows Server 2008 (32 or 64 bit)
- Windows Server 2012, 2012 R2
- RHEL 5. X, RHEL 6.X, Centos 5.X, Centos 6.X, SLES 10.X, SLES 11.X, Oracle Linux 5.X, Oracle Linux 6.X

MS Cluster is supported up to 8 node for Active/Active or Active/Passive configuration for physical or vmware. Supported OS – Windows Server 2008 R2, R2 SP1, Win 2012, Win 2012 R2
-CSV disk are not supported

Can perform protection, failback and DR drill

P2V supported for the following OS:
a) Physical server running- Win 2008 (32 or 64 bit), Win 2008 R2, Win 2012, Win2012 R2
b) VM on Win 2008 R2 Hyper-V - Win 2008 (64 bit), Win 2008 R2, Win 2012, Win2012 R2
c) VM on Win 2012 R2 Hyper-V - Win 2008 (64 bit), Win 2008 R2, Win 2012, Win2012 R2
d) Physical Server running – SLES 10 SP3 or higher, SLES 11 SP3 or higher, RHEL 5U8,5U9, 6U1,6U2,6u3 (64 bit), Centos 6U3, OL5U9 *

UEFI is not supported for Linux V2V or P2V
LVM2 is supported
Supported Linux fil system : ext3/4, ReiserFS
     CSV is not supported


Scenario 7: Migrate Amazon VM to Azure
Must deploy
- PS –on Amazon Web Services running on Windows Server 2012 R2
- CS & MT on Azure running on Windows Server 2012 R2

Perform unplanned failover to migrate from Amazon AWS EC2 VM to Microsoft Azure
Supported workload from Windows Server 2008 R2 SP1 or higher


Scenario 8: Migrate Azure VM Between Region


Migrate VM from one region to another region
Perform unplanned failover
Deploy the process server (running on Windows Server 2012 R2) on the same virtual network/subnet as the IaaS VMs you want to migrate.
Must deploy CS and MT running on Windows Server 2012 R2.


That's all folk, we will update this page when new enhancement on Azure Site Recovery (ASR)

Stay Tuned!

1 comment: