Azure Migrate (Hyper-V) Part 02

Check that these conditions are met before you begin. To install the appliance, either use the downloaded VHD file to establish a virtual machine on a host or operate the downloaded.zip file to run the PowerShell script on an existing physical or virtual system (running Windows Server 2016, with 16 GB of memory, eight vCPUs, around 80 GB of disk storage).

You must verify security if you picked the Zip file option. Before deploying a zipped file, make sure it’s safe.

in this Demo, we will use VHD Option and select “Download.”

After you download the Migrate Appliance, you need to be extracted it.

Then you need to continue with the import Virtual Machine Option and select the right path for the Migrate Appliance and continue adding the required “Memory and CPU Power to the Appliance.”

After you successfully add the Appliance VM, it should be visible in your Hyper-V Server.

Then login to the VM using the “Given password during the Setup” and visit the “IP Address” mentioned in Notepad located in Appliance Desktop.

Ensure you have internet in Appliance and wait until the prerequisite stage is completed.

Provide the Azure Migrate Project key you have generated in “Azure Portal Previously” (in this Demo Article Part 01)

Again, you need to verify the Login with “Azure PowerShell” with “Generated Code.”

Then add the Hyper-V host from “Add Source” and the “Server Credentials. “

Wait until finish the “Validation.”

Then go to Start “Discovery.”

Once Discovery is completed, visit the “Azure Portal.”

Visit Azure Migrate in Azure Portal, go for “Azure Migrate Assessment Tool”, and click the Access Select “Azure VM.”

Then you will automatically direct to the “Create Assessment” Section, and you can go to Assessment Settings to Edit the VM info.

Provide the necessary “Properties/ VM Size and Pricing Details” you plan to have, or you can use the Microsoft Recommended Settings.

Then select the Server(s) you need to migrate.

Then you can see the overview of the Assessment with “Cost Estimation.”

Then visit “Migration Tools” in Azure Migrate windows and Click Discover to complete the next step with “Azure Site Recovery.”

Select Virtualized Section as Hyper-V. Then Download & Install the Hyper-V Replication Provider software in your Hyper-V host. Also, download the “Registration Key File” to register the Hyper-V to the project.

Upload the “Key File” during the “Registration”

Use recommended “Proxy Settings” and start the “Registration” and finalise the “Discover Registration” in Azure Portal.

Go back to Azure Migrate windows and Select “Replicate.”

Select “Relevant Group and Assessment” and Mark the “Server(s)” click Next

Select the necessary options. (Eg: Resource Group and Vnet, you need to deploy the Server and Availability Options Etc.) and you also can use Azure Hybrid benefits if you have.

Review the configurations and start the replication.

Then check the status of the “Site Recovery Jobs.”

Once replication is completed, you will see the “Status as Protected.”

After delta replication is complete, you may do a test migration for the VMs before moving them to Azure completely. It is strongly recommended that you repeat this method for each machine at least once. From the Migrate menu, choose “Test Migration.”

Check the Test Migration Job in the Overview field and wait until all the stages are completed.

At the same time, you can see the Azure Deployed “Test Migrated VM.”

After verifying that the test migration works as expected, you can migrate the on-premises machines. Then go back to “Migration Tools” in Azure Migrate and perform the Migrate.

Select the Shutdown the VMs before migration to avoid the data loss

After waiting a few minutes Refresh the Migrate page, and the tiles on the Migrate page have been updated to show that you have a migrated server.

After completing the migration, right-click the VM and select “Stop replication.”

Then accomplishes the following goals:

· The on-premises machine’s replication is halted.

· Removes the machine from Azure Migrate: Server Migration’s Replicating server’s count.

· Cleans up the VM’s replication state information.

· Remove the on-premises virtual machines from your local virtual machine inventory.

· Update hostnames, database connection strings, and web server configurations once the app has been migrated.

Best practices for post-migration

· Back up Azure VMs with the Azure Backup service to keep your data safe.

· By replicating Azure VMs to a backup region and using Site Recovery, you can keep workloads operating and available.

For Azure VMs, always follow Microsoft’s recommended security procedures.