Sharon will demonstrate how to configure Azure Site Recovery. This process includes configuring the Azure Recovery Vault, setting up the host server, selecting virtual machines that require protection, and configuring recovery plans for failover. The failover and failback options will also be outlined.
- [Instructor] In this demo I'm gonna provide an overview of the Azure Site Recovery service. I have already pre-configured the service within Azure and I have set up the agent on server 2012 R2 to protect a virtual machine. We are gonna start in the Recovery Services vault in Azure. I had named this vault LyndaASR. Within this vault you're going to notice that I have one item that is being replicated. If I click in this Replicated items dialogue box, I will be provided some information about the replicated virtual machine.
In this case it is called LyndaDemo, and right now it is protected. If I click in a little bit further I now have some details about this particular virtual machine that is being protected. I know it's a Windows operating system, I know the storage account that the virtual machine has been replicated to, it's called LyndaASR, I have a replication policy called LyndaASR associated to this virtual machine. One of the nice things with ASR, when it evaluates your on-premise virtual machines, it will associate the appropriate size Azure virtual machine to match the on-premise virtual machine size.
In this case Azure has selected a Basic_A1. This is what it looks like from the Azure portal. I am now gonna flip over to my server. This happens to be an on-premise server with a host operating system of server 2012 R2. I have HyperV running on this server, and one virtual machine, it is that single virtual machine that is being replicated to Azure. You are now looking at an on-premise physical server with one virtual machine configured.
In this case the virtual machine is off. If this virtual machine was on and running, the replication would still be occurring. In the Replication tab of HyperV Manager I can see that my Replica Server happens to be Microsoft Azure. I am now gonna flip back to the Azure portal. We have three options for failover. Test Failover will allow us to failover into that virtual machine without disrupting our current environment, a Planned Failover is when we know that our on-premise environment will not be accessible, and then there the Planned Failover, this is reactive.
Our on-premise environment is no longer accessible. If we knew that that on-premise virtual machine was going to be down, let's say for maintenance, we would come in and select a Planned Failover. At this point we would have our Failover direction, so we're going from LyndaASR into Microsoft Azure. We would click OK, at this point, our virtual machine in Azure would spin up and we would be able to access it. For this demonstration we will not see that virtual machine fully running.
And finally, because we are replicating our on-premise virtual machines into Azure, again, we can leverage Azure as a migration tool. Once our machines are fully replicated into Azure, we can go ahead and run them in Azure. We never have to fail them back. Azure Site Recovery supports different scenarios and different backup methodologies. For detailed instructions on how to configure for your specific workloads, please refer to the links in the handout.
- Understanding cloud technologies
- Why Azure?
- Creating virtual networks and storage
- Using Azure Active Directory for identity management and protection
- Disaster recovery with Azure Backup and Azure Site Recovery
- Working with virtual machines