Azure Migrate, post migration state.

Nick Smith 0 Reputation points
2023-02-11T20:09:47.63+00:00

Hi,

I am looking to migrate several VM's from Hyper-v into Azure. I have got all the way through the setup (assessment tool and test migration tool). I am now ready to migrate one of my VM's over.

There is an option to shutdown the VM to prevent data loss, which is fine but I have two questions, post migration:

  1. Does the VM in Hyper-V remain where it is and unchanged (as in, Azure migrate doesn't delete it as part of a clean up process)
  2. If the answer to the above is yes, the VM also remains in Hyper-V, will Azure Migrate spin it back up?

I ask, I want to do some testing in the migrated VM that hits Azure before it goes into Production. So I will need the other VM accessible by the users to access a database.

Thanks in advance,

Nick

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
717 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,538 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. risolis 8,701 Reputation points
    2023-02-11T22:55:51.9633333+00:00

    Hello @nick smith

    Thank you for posting this concern on this community space.

    Here are my 2 cents, for this case scenario and I want to gather the following statements down below:

    1- See the image

    User's image

    2-Note

    For minimal data loss, the recommendation is to bring the application down manually as part of the migration window (don't let the applications accept any connections) and then initiate the migration. The server needs to be kept running, so remaining changes can be synchronized before the migration is completed.

    Finally, you have to remember that this Azure migration feature vs the Azure Site recovery feature is agentless which can give you a tiebreaker detail. When there is an agent installed this will be in charge of marking the VM server as protected or unprotected status.

    Let me know if that was useful but if not, I can keep assisting you further.

    Looking forward to your feedback,

    Cheers,

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

  2. SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee
    2023-03-28T11:04:08.03+00:00

    Hi @Nick Smith Thank you for contacting us. Happy to answer any questions you may have!

    1. Does the VM in Hyper-V remain where it is and unchanged (as in, Azure migrate doesn't delete it as part of a clean-up process) Azure Migrate does not delete the Hyper-V VM as part of the clean-up process. The clean-up process only removes the Azure resources that were created during the migration process, such as the Azure VM, the network interface, and the storage account. The Hyper-V VM remains intact and can be used for other purposes.
    2. If the answer to the above is yes, the VM also remains in Hyper-V, will Azure Migrate spin it back up?
      No. There is no roll back mechanism. User's image

    Reference link for common questions - https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/migrate/common-questions-server-migration.md

    Recommendation: For your scenario, you can perform test migration. For more details, refer to the document - https://learn.microsoft.com/en-us/azure/migrate/how-to-test-replicating-virtual-machines

    Hope this helps. Feel free to ping with questions for further assistance.

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