Failback with destroyed HyperV host

Tyler Saville 431

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

3 answers

RevelinoB 2,780 Reputation points

2023-04-24T14:10:41.54+00:00
how to failback using Azure Site Recovery when your Hyper-V host is destroyed. Here are the general steps:

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.

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.

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.

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.

Initiate failback: Once the failback is configured, initiate the failback process by clicking "Start Failback" and monitor the progress.

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.
Please sign in to rate this answer.
Tyler Saville 431 Reputation points

2023-04-24T14:16:11.6466667+00:00

So you have to have a site-to-site VPN or connection from on-prem to azure?

RevelinoB 2,780 Reputation points

2023-04-24T14:47:23.2+00:00

Yes, in order to use Azure Site Recovery for failover and failback, you need to have a site-to-site VPN or ExpressRoute connection between your on-premises infrastructure and Azure. This allows the replication and movement of data between the two environments, as well as the ability to manage and orchestrate failover and failback processes.

Tyler Saville 431 Reputation points

2023-04-24T14:58:13.27+00:00

This is not true for modernized architecture according to MS documentation - you don't need vpn to failback. Are you saying with HyperV setup that a VPN is still required?

RevelinoB 2,780 Reputation points

2023-04-24T15:33:46.5+00:00

I apologize for the confusion in my previous message. You are correct that a VPN connection is not required for failback using Azure Site Recovery. In a Hyper-V setup, you can use Azure Site Recovery to replicate virtual machines to Azure without requiring a VPN connection. Once the replication is complete, you can then fail over to Azure in the event of a disaster. When you are ready to failback, you can initiate a failback operation from Azure Site Recovery, which will replicate the virtual machines back to your on-premises environment. The failback process involves several steps, and the exact steps will depend on the specific details of your setup. However, in general, the failback process involves stopping the replication of virtual machines to Azure, synchronizing any changes that occurred during the failover period, and then replicating the virtual machines back to the on-premises environment. You will need to ensure that your on-premises environment is configured to receive the virtual machines being replicated back from Azure, and that any necessary network configurations are in place. I hope this clears up any confusion. If you have any further questions, please feel free to ask.

RevelinoB 2,780 Reputation points

2023-04-24T15:35:01.52+00:00

I apologize for the confusion in my previous message. You are correct that a VPN connection is not required for failback using Azure Site Recovery. In a Hyper-V setup, you can use Azure Site Recovery to replicate virtual machines to Azure without requiring a VPN connection. Once the replication is complete, you can then fail over to Azure in the event of a disaster. When you are ready to failback, you can initiate a failback operation from Azure Site Recovery, which will replicate the virtual machines back to your on-premises environment. The failback process involves several steps, and the exact steps will depend on the specific details of your setup. However, in general, the failback process involves stopping the replication of virtual machines to Azure, synchronizing any changes that occurred during the failover period, and then replicating the virtual machines back to the on-premises environment. You will need to ensure that your on-premises environment is configured to receive the virtual machines being replicated back from Azure, and that any necessary network configurations are in place. I hope this clears up any confusion. If you have any further questions, please feel free to ask.

Tyler Saville 431 Reputation points

2023-04-24T15:39:06.77+00:00

I would like clarification on the scenario where the HyperV host is destroyed and we have to build a new host to failback from azure. What are the steps next? New hyperv site in azure? Register it to same site? Need each step please. Thank you

RevelinoB 2,780 Reputation points

2023-04-24T15:43:29.3833333+00:00

If the Hyper-V host is destroyed and you need to fail back from Azure, you would need to follow the below steps:

Deploy a new Hyper-V host on-premises with the same configuration as the original one.

Create a new Azure Site Recovery (ASR) replication job and set up replication to the new Hyper-V host.

Once replication is complete, perform a test failover to ensure that the new Hyper-V host is working correctly.

When you are ready to perform the actual failback, you will need to stop replication from the Azure portal.

Shut down the virtual machines on the Azure side and initiate a failback from the Azure portal. This will bring the virtual machines back to the on-premises Hyper-V host.

Once the failback is complete, reconfigure replication to the original on-premises Hyper-V host to resume normal replication.

Finally, you can decommission the new Hyper-V host that was used for failback. Note that these steps may vary depending on the specific configuration and requirements of your environment.
Sign in to comment
SadiqhAhmed-MSFT 41,721 Reputation points Microsoft Employee

2023-05-04T19:48:57.9566667+00:00

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

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/hyper-v-azure-failback.md#fail-back-to-an-alternate-location

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
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Tyler Saville 431 Reputation points

2023-05-04T19:53:56.2733333+00:00

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!
Please sign in to rate this answer.
SadiqhAhmed-MSFT 41,721 Reputation points Microsoft Employee

2023-05-04T20:08:45.0933333+00:00

@Tyler Saville Thats great to hear. Thank you for posting an update. If by any chance my response was helpful, please do "Accept Answer" and up-vote it
Sign in to comment

Share via

Failback with destroyed HyperV host

3 answers