During this video, Sharon demonstrates the steps and configuration required to successfully initiate a planned or unplanned failover of protected virtual machines.
- [Instructor] Once you have completed a test failover and everything works properly, you can then be confident about when a real failure happens, and you have two options for initiating a failover. You have a planned failover, and you would use this for when you knew the on-premise environment was going to be down for repairs, et cetera. Then you have the unplanned failover. In this case, for some reason, the on-premise environment is no longer up and running. It could be a power failure, it could be a fire or flood.
It could be a hardware failure. And then you would use the failover option. Let's go ahead and select Failover, and we're going to pretend that we actually have a failover. Here, you'll notice we have our failover direction. Again, we're going from that HyperVvm server to Azure, and then we can go ahead and choose our recovery point. Next, you'll want to shut down the virtual machines and synchronize the latest data. When you're doing a planned failover, you should always select the shutdown option, but this may not be an option in an unplanned failover mode.
If you do not select to shut down the virtual machines and synchronize, then the latest recovery point will be used for that failover. Once you've done that, you go ahead and click OK. And just like the test failover, because these machines have already been replicated, they just need to be started. After a few minutes, your status will change to Failover Complete, and you'll notice you have the option to select Commit. We'll talk about that in a moment. You'll also notice under the infrastructure view your diagram is gone.
So let's go ahead and scroll over. You'll notice that our virtual machine is now here and it's only called VM dash test. And we can see our virtual machine is there. If you find you cannot connect to your virtual machine, it might have been because you forgot to allow remote connections in the virtual machine. So make sure you double check that. Okay, let's go back to our recovery services vault.
I'll scroll back over. And you'll now notice in our overview our number's a little different. We have one that's critical, we have one healthy, that happens to be VM2. And not applicable, and this will be VM1. Let's go ahead and take a look at the replicated items. And you'll notice here that we have VM1, where it states failover is complete.
At this point, we can go ahead and click Commit. At this point, if you click Commit, the virtual machine will now be in Azure, and there will be no recovery point for that virtual machine. So I'm going to go ahead and click OK. And this will take a few moments, and that's all there is to failing over to your virtual machines in Azure.
- 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