What is Azure Site Recovery (ASR)?
An important part of your organization’s business continuity and disaster recovery (BCDR) strategy is figuring out how to keep corporate workloads and apps up and running when planned and unplanned outages occur.
Site Recovery helps do this by orchestrating replication, fail-over, and recovery of workloads and apps so that they’ll be available from a secondary location if your primary location goes down.
ASR can also be used as a migration tool to replicate protected servers into Azure IaaS.
Why use Site Recovery?
Here’s what Site Recovery can do for your business:
- Simplify your BCDR strategy—Site Recovery makes it easy to handle replication, fail-over and recovery of multiple business workloads to Azure.
- Provide flexible replication—Using Site Recovery you can replicate workloads running on Hyper-V virtual machines, VMware virtual machines, and Windows/Linux physical servers.
- Easy fail-over and recovery—Site Recovery provides zero data loss test fail overs to support disaster recovery drills without affecting production environments. After fail-over you can fail back to your primary sites. Site Recovery provides recovery plans that can include scripts and Azure automation workbooks so that you can customize fail-over and recovery of multi-tier applications.
- Eliminate secondary data-center—You can replicate to a secondary on-premises site, or to Azure. Using Azure as a destination for disaster recovery eliminates the cost and complexity maintaining a secondary site, and replicated data is stored in Azure Storage, with all the resilience that provides.
- Integrate with existing BCDR technologies—Site Recovery partners with other application BCDR features. For example you can use Site Recovery to protect the SQL Server back end of corporate workloads, including native support for SQL Server AlwaysOn to manage the fail-over of availability groups.
What can I replicate?
What is the implementation process for SR Cloud Solutions?
1.) Capacity Planning – SR Cloud Solutions make use of the Azure Site Recovery Capacity Planner tool that helps us to figure out your capacity requirements for protecting Hyper-V VMs, VMware VMs, and Windows/Linux physical servers with Azure Site Recovery.
2.) Network Mapping — Design considerations at this stage will include whether to use a stretched subnet between the primary and secondary DR sites or make use of different IP address assignments using a subnet fail-over technique.
3.) Replicate VM Workloads – We will setup the InMage Scout agents and associated ASR replication servers, we will monitor the replication of each of your servers either to a secondary DR site or into Azure.
4.) Fail Over Testing & Handover – Both fail over and fail back testing will be conducted between the primary and secondary DR sites to ensure the ASR BCDR process is within the clients requirements. At the end of the project, all BCDR documentation will be compiled and handed over to the client to form a part of their BCP documentation.