Planned Fail over - aftermath

Johnathan Copeland 41 Reputation points
2021-01-05T15:07:12.86+00:00

I have performed a planned fail-over on a VM from HyperV - this was successful, the VM in HyperV powered down, and booted up in Azure and is running and accessible.

In my recovery services vault, the VM replication is still there, I have the option to "Commit" , "Disable" or "Complete Migration"

I not longer want to run the replication for this HyperV machine it is no longer needed, which option do I select, I do not want to affect the VM that is now running in Azure, it has been running for over a month now with out any issues.

I'm finding it difficult in the documentation on what each option does directly and what affects it will have if any on the Azure VM.

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
708 questions
0 comments
Accepted answer
  1. SadiqhAhmed-MSFT 45,181 Reputation points Microsoft Employee
    2021-01-06T12:40:36.357+00:00

    @Catalyph Thank you and appreciate your patience in this matter.

    According to the description, it looks like the Hyper-V machine was migrated to Azure using ASR. The three options that you describe all serve different purposes -

    1. Complete migration means that the customer will not go back to the source anymore. They migrated over to Azure and now they're done. Clicking on ‘Complete Migration’ triggers ‘Commit’ and then ‘Disable Replication’ internally.
    2. Commit means that this is not the end. The replication item along with all the configuration will remain, and the customer can hit ‘Re-protect’ at a later point in time.
    3. Disable will disable the replication and remove all the related configuration. It won’t affect the already existing Azure VM.

    As you have mentioned that you don’t want to run the replication for the Hyper-V machine anymore, Complete Migration should be the way for you to go. It won’t affect the Azure VM.

    Please take a moment to "Mark as Answer" and "Vote as Helpful" wherever applicable. Thanks!

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SUNOJ KUMAR YELURU 14,051 Reputation points MVP
    2021-01-05T15:28:19.023+00:00

    @JohnathanCopeland-2771

    After validation, select Commit to finalize the recovery point of the VM after failover. After you commit, all the other available recovery points are deleted. This step completes the failover.

    To stop replication then option "disable"

    Did you performed below steps in fail-over?

    Fail over to Azure
    In Settings > Replicated items, click the VM > Failover.
    In Failover, select the Latest recovery point.
    Select Shut down machine before beginning failover. Site Recovery attempts to do a shutdown of source VMs before triggering the failover. Failover continues even if shutdown fails. You can follow the failover progress on the Jobs page.
    After you verify the failover, click Commit. It deletes all the available recovery points.

    refer - https://video2.skills-academy.com/en-us/azure/site-recovery/hyper-v-azure-failover-failback-tutorial

    ----------

    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.
  2. SUNOJ KUMAR YELURU 14,051 Reputation points MVP
    2021-01-06T02:13:36.543+00:00

    @Catalyph

    If you don't want to run replication then you can do disable replication in azure portal.

    Before doing, Please enable backup and run on the azure vm.

    If this answers your query, do click “Accept Answer” and Up-Vote for the same. And, if you have any further query do let us know.

    0 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.