During this video, you can learn how to replicated an Azure virtual machine to another region for either protection during a regional outage as a method to migrate Azure virtual machines from one region to another.
- [Instructor] Not only can you protect your virtual machines on physical hosts, but you can also use Azure site recovery to protect your Azure virtual machines. You can replicate your virtual machines to another region, providing business continuity by keeping your apps up and running during unplanned and planned outages. The process of replicating a virtual machine to another region is incredibly simple, and I'll show you how to do it now. As you can see, we've logged into Azure, and we're looking at the overview for a virtual machine called "Source." In order to configure replication, you'll need to scroll down to operations and then disaster recovery.
And you'll notice that it states that this is in preview. As of today's recording date in late February 2018, it is in preview. Now we can go ahead and set up the replication. The first thing we need to do is set our target region. And again, you can pick and choose as is. Next, we can go ahead and select the target VM resource group. And you'll notice here that it says "new." I have not made a VmMigration-asr resource group. That has been created for me.
My virtual machine is not in an availability set, and therefore an availability set will not be presented. And as for a virtual network, a new one will be created as well. If I scroll down, we can see that a new target storage account will be created as well as a new cache storage account. The existing recovery services vault will be used for this and a new replication policy will be created. If you scroll down a little bit more, you'll see a map of where you can actually replicate to.
You'll notice the blue states for the source region, so that's where that VM currently sits. The selected target is in purple. But I could replicate to other regions within the United States. Go ahead, click on "Enable Replication." As that's validating, one thing I do need to point out is your virtual machine must be running in order to enable replication. If your virtual machine is shut off, you will have a warning. You'll also notice at the bottom of this page, it says "Creating Azure resources." Do not close this blade.
For that reason, we'll wait. Once the messages have cleared, you can go ahead and pop into that new resource group. I'm going to go ahead, list my resource groups, and you'll notice that I have several here. And we're actually looking for the resource group VmMigration-asr, and this was a new one that was created for us when we replicated that virtual machine. And now you'll notice that we do have a new network, and the other resources will populate as that virtual machine is migrated.
It may take some time for your virtual machine to start replicating. The easiest way to see the status is to pop into the disaster recovery blade of your virtual machine. And as we can see here, we can see the recovery services vault that was used for this replication. Now one thing I want to point out here, is I did not have a choice on the vault itself. It chose a vault that was in that region. So keep that in mind. We can also see other information about that VM that we are now protecting.
We can see the replication health is healthy. It's protective, and our appeal is one minute. We also can see our crash-consistent and app-consistent recovery points. If we scroll down a little bit, you can actually see that replication in action between Canada central and Canada east. And just like we did previously, we can go ahead and do a test failover or a full failover as required. As we've already seen these in action, I'm just going to leave them.
And if we wanted to stop this replication, go ahead click on "More" and disable replication. Microsoft would like to know why you are no longer replicating this. So I'm going to go ahead, I'm doing a proof of concept. I can leave the answer as yes and click OK. And now the replication will be disabled. As you can see, using disaster recovery is a great way to not only protect your Azure Vms, but you can also use this to move your Azure Vms to other regions.
- Creating a Recovery Services vault for Azure Backup
- Protecting virtual machines, files and folders, databases, workloads, and file shares
- Restoring virtual machines, files and folders, databases, workloads, and file shares
- Azure Site Recovery scenarios
- Running failover and failback tests
- Replicating an Azure virtual machine