Failback with destroyed HyperV host

Tyler Saville 391 Reputation points

Is there documentation on how to failback (azure site recovery) when your HyperV host is destroyed? What are the steps? Thank you

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
646 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. RevelinoB 2,775 Reputation points

    how to failback using Azure Site Recovery when your Hyper-V host is destroyed. Here are the general steps:

    1. Restore the on-premises Hyper-V host: You will need to rebuild the on-premises Hyper-V host using new hardware or restoring from a backup if possible.
    2. Reconfigure the virtual network: If the virtual network was configured differently on the restored Hyper-V host, you will need to reconfigure the virtual network on the virtual machines in Azure before you can start the failback process.
    3. Test connectivity: Ensure that the restored Hyper-V host can communicate with the virtual machines in Azure by pinging them and ensuring that the virtual machines can communicate back.
    4. Configure failback: To initiate the failback process, go to the Azure Site Recovery vault and select the "Replicated Items" tab. Select the virtual machine that you want to failback, and click "Failback". Follow the prompts to configure the failback process, including selecting the restored Hyper-V host as the target.
    5. Initiate failback: Once the failback is configured, initiate the failback process by clicking "Start Failback" and monitor the progress.
    6. Cleanup: Once the failback is complete, clean up the Azure resources by deleting the Azure virtual machines and related resources that were created during the failover process. Don't forget the above steps are general guidelines, and the exact steps may differ depending on your specific environment and the nature of the disaster. It's always recommended to review the official Azure Site Recovery documentation.

  2. SadiqhAhmed-MSFT 39,126 Reputation points Microsoft Employee

    @Tyler Saville You can setup a new Hyper-V host and failback to that:

    Option #2: Would be to download the VHD disks from Azure and attach them to new VMs on the Hyper-V on-prem.

    If the failback /re-sync has already failed for some reason, then you can only use option 2.

    If the response helped, do "Accept Answer" and up-vote it

    0 comments No comments

  3. Tyler Saville 391 Reputation points

    I figured it out in my lab, you have to build a new host and add it as a new server within the same hyper-v site, easy as that!