Azure Site Recovery between #Azure regions #IaaS not for Managed Disks and Server 2016 #Cloud #Winserv #legacy

You can migrate Azure VMs between regions using Site Recovery. In other words, you can replicate the Azure VMs and fail them over to another region. In this blog we set up a Recovery Services vault, deploy an Azure configuration server to manage replication, add it to the vault, and specify replication settings. Enable replication for the machines you want to migrate, and run a quick test failover. Then you run an unplanned failover with the Complete Migration option. Seems easy and it is all in Azure. In my other blog post I’ll covered the other ASR scenarios .

https://robertsmit.wordpress.com/2017/02/07/replicate-hyper-v-virtual-machines-to-azure-using-azure-site-recovery-asr-bcdr-winserv-cloud-msoms/

https://robertsmit.wordpress.com/2014/08/27/azure-site-recovery-service-asrs-hyper-v-to-azure-recovery-mvpbuzz/

https://robertsmit.wordpress.com/?s=ASR

But an Important lesson always look for “Is my System Supported “

Support for Azure to Azure replicated machine OS versions

The below support is applicable for any workload running on the mentioned OS.

Windows

64-bit Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2 with at least SP1

Linux

Red Hat Enterprise Linux 6.7, 6.8, 7.1, 7.2, 7.3

CentOS 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3

Oracle Enterprise Linux 6.4, 6.5 running either the Red Hat compatible kernel or Unbreakable Enterprise Kernel Release 3 (UEK3)

SUSE Linux Enterprise Server 11 SP3

Lets build this configuration

First we go to the Recovery service and create a new vault.

Place this vault where every you want.

the Next step is creating a Site Recovery configuration and choose the VM’s that need protection.

As we are using Azure as a Base we don’t need any infrastructure preparations. It is just an easy Click. Unless….

The First step is selecting the Source Resource Group and Region

The Second step is picking the VM’s to protect. And as Microsoft is hamering on “use Managed disks” Well there is an little Issue.

Ok that is an Issue can’t move this VM’s to an other Region. But it is a preview so plenty of time to fix this. Or is it to Soon for Managed disk ? Well that’s an other discussion and maybe a new Blog post about Managed disks – What Not to do.

After We select the VM to Protect and the Portal pops up a suggested configuration but you can change this in the customize settings

I leave this all to default

But the Retention Policy need to change but this is all up to you.

After this the system does a validated and then you can Enable the Replication. And then we wait.

But What ? an Error eh everything looks ok. Lets check the Error log in Azure

ARM debug yes check been there done that.

code": "151021", "message": "Site recovery extension does not support the Windows operating system running on the virtual machine."

Is there something Wrong with My Server ? I could It is a DC and I never logon to this locally Let me check the Server.

It is Running and the Agent is healthy Ah but I need to change My password could this be the Issue ?

Still Let me dive a bit deeper in the Azure Logging I checked the Replication Policy In the Portal.

But wait there is more a web link As I did not Read the Requirements for Azure to Azure Replication.

https://aka.ms/a2a-os-support-matrix

Support for replicated machine OS versions

The below support is applicable for any workload running on the mentioned OS.

Windows

64-bit Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2 with at least SP1

So no Windows Server 2016 so far the Replication from and to Azure. All my servers are 2016 and I’m not going Back. just need to wait for the next preview update.

https://aka.ms/a2a-os-support-matrix

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Http://nl.linkedin.com/in/robertsmit

Google Me : https://www.google.nl

Bing Me : http://tinyurl.com/j6ny39w

LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog