Question about failback from Azure to VMware using ASR

Max Tevs 0 Reputation points
2025-05-01T23:13:21.43+00:00

Hello,

We are developing a DR playbook for one of our clients. The client runs primarily in a VMware environment, and Azure will be the DR target.

I need some clarification around what scenarios are and are not supported. We have tested planned failovers from VMware to Azure, then from Azure back to VMware successfully. In this case, the original location was used to replicate back from Azure to VMWare.

How about in situations where the original datacenter no longer exists, and a brand new VMware environment with brand new hardware is provisioned? The following article states that the original vCenter and Configuration server need exist for any replications and failbacks from Azure to VMware

https://learn.microsoft.com/en-us/azure/site-recovery/concepts-types-of-failback

However some other articles seem to suggest failing back into new vCenters is possible. Can anyone clarify if a failback to VMWare in the case where a brand new VMWare environment was provisioned is or is not possible? Is alternate location recovery strictly in the event that the original VM itself does does not exist?

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

1 answer

Sort by: Most helpful
  1. Vinod Pittala 1,750 Reputation points Microsoft External Staff
    2025-05-02T02:49:40.0566667+00:00

    Hello Max Tevs,

    Yes, failing back from Azure to new vCenters is possible by considering it as a failback to an alternate location. However, it is crucial to ensure that the new environment is properly configured to replicate the original setup as closely as possible. This includes setting up a new vCenter and a new configuration server or appliance that can communicate with Azure Site Recovery.

    If the on-premises virtual machine or vCenter doesn't exist before reprotecting the virtual machine, the scenario is called an alternate location recovery.

    The reprotected workflow creates and recovers the virtual machine to the same ESX host on which the master target server is deployed. This includes any datastore managed by vCenter on which the appliance is situated and is accessible (with read and write permissions) by the appliance, can be chosen (original/new).

    Note: you can fail back only to a virtual machine file system (VMFS) or vSAN datastore. If you have a (RDM), reprotect and failback won't work.

    The following article states that the original vCenter and Configuration server need exist for any replications and failbacks from Azure to VMware

    The original vCenter and Configuration server are needed if you intend to failback to the original location. because you can't deploy a new configuration server to an existing vCenter, nor you add a new vCenter to the existing configuration server and failback into the new vCenter. hence in original location recovery we need the same vCenter and Configuration server. However, in alternative location recovery we need a new vCenter and configuration server or appliance.

    Below link is to Set up a process server in Azure for failback:-

    https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-set-up-process-server-azure?source=recommendations

    I hope this clears your doubts. If you have any further questions, feel free to ask.


    If you found this informative, please consider accepting an answer as a token of appreciation. And don't forget to give it a thumbs up 👍 if it was helpful.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.