In this lesson, you can learn how to configure and fail back your Hyper-V virtual machines after a planned or unplanned failover.
- [Instructor] And the final step of failing over into Azure is the ability to fail back. In the example that we used where we had an issue on-premise, once that issue was resolved, whether it be a hardware failure or a power outage, we can go ahead and fail back. And it's very easy to do. We're back into the VM1 replicated items. And you'll notice here, we can go ahead and click on planned failover. And this time you'll notice their failover direction is from Azure to our Hyper-V server.
Next you have a data sync option. So you can minimize the downtime or you can do a full download. I'm going to go ahead and select minimize downtime. And our last option is to create the VM on-premise if that virtual machine does not already exist. So let's say it was a hardware failure and you had to rebuild the virtual machine, this would allow you to do so. You would go ahead, select hyperv, and off it goes. I don't need to do that, so I'm just going to go ahead and click OK.
And again, the failover could take some time, depending on your bandwidth and connection to your on-premise environment. Once your data has synced back to your on-premise environment, you'll notice that the status will change to data sync complete. We're not quite done yet. If we go ahead and select data sync is complete, you'll notice that we have another blade that pops open. And we can see the properties of this job, we can see the statuses of the job, but note that the last status says, waiting for user input.
This is required for us, the operator, to come up and click complete failover. We're then presented with, are you sure that you want to do this? And yes I do, so I'm going to go ahead and click yes. And again, this could take some time. But once it's done, the last step in this process is to select commit. And as before, we're prompted, are we sure we want to commit the virtual machine? Yes we do because we do want to fail back.
And go ahead, select OK. And as before, this will take some time. But that's all there is to it to failing back to your on-premise environment from 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