Backup & Storage|Microsoft Azure|Security

Azure Site Recovery for Azure Virtual Machines

In this post, I will explain how a new preview feature, Azure Site Recovery for Azure Virtual Machines, can provide disaster recovery services for virtual machines that are running in Azure.

 

 

Sponsored Content

What is “Inside Microsoft Teams”?

“Inside Microsoft Teams” is a webcast series, now in Season 4 for IT pros hosted by Microsoft Product Manager, Stephen Rose. Stephen & his guests comprised of customers, partners, and real-world experts share best practices of planning, deploying, adopting, managing, and securing Teams. You can watch any episode at your convenience, find resources, blogs, reviews of accessories certified for Teams, bonus clips, and information regarding upcoming live broadcasts. Our next episode, “Polaris Inc., and Microsoft Teams- Reinventing how we work and play” will be airing on Oct. 28th from 10-11am PST.

Avoiding Downtime

Disaster recovery is a hot topic. British Airways has had days of flight issues because of data center and power issues. AWS had a massive outage in one of its regions in February. WannaCrypt/WannaCry has made everyone think about dat availability, services availability, and security.

I wrote an article back in March that discusses how to avoid AWS-style outages when deploying virtual machine-based services in Azure. In that article, I explained that despite the myths and assumptions, neither AWS or Azure replicates virtual machines for you to another region. If that region goes offline, as has happened to AWS US East in Virignia many times now, then anything you have there will stay offline. No magic fairies are sprinkling dust to wormhole your machines and data to another online region.

This means that you have to deploy duplicate virtual machine builds, mirror the application installations and maintenance, enable inter-region connectivity, and replicate data from one region to another. In the event of an outage in a cloud service region, you need to have more than double the amount of effort and costs to ensure business continuity. Until now…

Azure-to-Azure Site Recovery

Microsoft has launched a preview service that allows you to optionally replicate virtual machines from one region to another close-by region. For example, virtual machines running in North Europe (Dublin) can be replicated to one of the following: UK West (Wales), UK South (London), or West Europe (Amsterdam).

This cluster of regions is referred to as a geographic cluster. The following clusters are available for replicating virtual machines in Azure:

The Azure to Azure Site Recovery geographic clusters [Image Credit: Microsoft]
The Azure-To-Azure Site Recovery Geographic Clusters [Image Credit: Microsoft]
 

The solution is based on mature technologies. The Azure recovery services vault, placed in another region from the production virtual machines, provides management and orchestration. A Mobility Service from InMage Scout virtual machine extension provides the replication functionality. Think of it as an Azure-managed virtual machine integration service. No, Azure is not using Hyper-V Replica. There are a few differences:

  • Replication is continuous. Instead of being interval-based, it is still asynchronous for range and performance reasons.
  • Replication is based on a filter driver in the guest OS or the Mobility Service. It is not a change log stored with the virtual hard disk.

As a result of the latter, there is a smaller compatibility list than you will find for private site-Azure replication when using Hyper-V hosts. The Mobility Service only supports a subset of Azure compatible OS today:

Supported guest operating systems for Azure-to-Azure site recovery [Image Credit: Microsoft]
Supported Guest Operating Systems for Azure-to-Azure Site Recovery [Image Credit: Microsoft]
There are some notable missing OS:

  • Ubuntu
  • Windows Server 2016

However, this is a preview release, so things can change as we move toward general availability.

This new DR feature is an as-a-service option. This means that you require limited engineering to get things going. A simple recovery services vault and resource group in another region in the geographic cluster will do the trick. You can simply enable replication for each required virtual machine. Azure Site Recovery will create any required dependencies such as storage accounts, networks, and subnets. Names are based on the original deployment and a suffix is added. You can customize the naming.

Replicating Azure virtual machines to another region [Image Credit: Microsoft]
Replicating Azure Virtual Machines to Another Region [Image Credit: Microsoft]
 

A default replication policy is offered but you can customize it. Configuring how recovery points are kept and how many of those points are application consistent, are a few examples of how you can customize.

Some of the usual features of Azure Site Recovery are there to use. An important one is the ability to run a non-disruptive test failover. With this ability, you can test your failover and ensure that if a region fails, your business can survive in another region.

Region Mobility

Azure veterans should already be aware that Azure Site Recovery offers customers the ability to “lift and shift” migrate virtual machines from VMware or Hyper-V to Azure. It is free of cost if the process is completed within 31 days, per virtual machine. You simply enable replication, perform a test failover, do a planned failover, commit the action, and strip away replication.

Azure-to-Azure Site Recovery will offer region mobility for customers that wish to relocate their services. For example, customers in the UK might choose to relocate from North Europe or West Europe might choose to relocate to one of the UK regions.

BECOME A PETRI MEMBER:

Don't have a login but want to join the conversation? Sign up for a Petri Account

Register
Comments (0)

Leave a Reply

Aidan Finn, Microsoft Most Valuable Professional (MVP), has been working in IT since 1996. He has worked as a consultant and administrator for the likes of Innofactor Norway, Amdahl DMR, Fujitsu, Barclays and Hypo Real Estate Bank International where he dealt with large and complex IT infrastructures and MicroWarehouse Ltd. where he worked with Microsoft partners in the small/medium business space.
External Sharing and Guest User Access in Microsoft 365 and Teams

This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

You will learn:

  • Who should be allowed to be invited as a guest?
  • What type of guests should be able to access files in SharePoint and OneDrive?
  • How should guests be offboarded?
  • How should you determine who has access to sensitive information in your environment?

Sponsored by: