Now that we have our north Europe Classic VM replicated to west Europe storage account, it is time to hit the unplanned failover button and see what’s happening.
In this post we will configure the Classic VM replication scenario and initiate the synchronization between our sites.
In this post we will create the West Europe Resource Group, storage account and VNet which will be used as the “target” infrastructure for the replicated Classic VM.
In this post we will install the Mobility Service agent on our Classic VM and touch on the networking challenges we have with this design.
The Process Server is the most important component in a deployment like ours. It is the one responsible for handling all compute and IO intensive aspects of replication and maintaining replication policies, replication status and health reports.
About two weeks ago, Azure Site Recovery (ASR) V2 was released to preview. Using the “Unplanned Failover” we can perform ASM (Classic / V1) VM to Azure Resource Manager (ARM) VM conversion.
About a week ago Veeam introduced “Direct Restore to Azure”. In the last couple of days, I’ve been playing with it and I have to say I was surprised to see how easy it is to take a backup file and make an Azure VM out of it.
Lately I’ve been playing around with Azure DevTest labs. This is a great way for provisioning rapidly deployed policy-driven environments in Azure for developers, testing, QA, DevOps and other teams in the organization.