About two weeks ago the public preview was announced for an Azure-to-Azure site recovery service (DR). This was a highly anticipated service to me. So I’m glad it was announced! Today’s post will be on doing a quick setup of the service to get an insight into the look & feel.
What will we be doing today? We’re going to replicate a machine from “West Europe” to “South UK”.
What will the flow be? We’ll have a “Site Recovery Vault” in the target destination. Why? This to ensure that we can leverage the service when the source region went offline. In the source region, we’ll have our VM + Storage Account / Disks, but also a storage account used for caching. All changes make to the disk, will be stored in that cache. On the target side, we’ll have a storage account where a replica (and retention points) of the VM will be kept. Sound pretty easy? Let’s find out…
Let’s go to the marketplace and type “oms” ;
Select “Backup and Site Recovery (OMS)”, and we’ll deploy that one to “UK South”.
Next up, select the VM(s) you want to replicate.
This as it looks just the same as my source VM.
As I’m happy with my failover test, let’s clean up the resources.
If a machine is grayed out on the selection, this means that the machine is not in a running state!
If you are very eager, you might see the following error message. This means that the VM is running, but the VM agent isn’t ready yet. Have some patience… 😉
After the cleanup, be sure to also cleanup the resources you created additionally… Like the public ip address!
Check the support matrix… At this time there are several “gotchas” ; windows 2016 support, managed disks support, limited amount of regions, … Though these will get fixed by the time this service will be “General Available”.
Any Enterprise looking to leverage Azure needs to have a BCP/DRP. Azure Site Recovery services shows that it has the capabilities to support this. When test-driving this service, I must say the process was very smooth. As I’ve done several “hybrid” ASR deployments, I must say those cost a bit more time, despite even being quite easy in setup.