Azure Migration Services – Easy Cloud Migration Services #Azure #Cloud #ASR #Migrate #azops #VMware #Database

This blog post is a bit long sorry for this tons of screen shots to give you more detail. This is all based on Hyper-v but the same steps are there for Vmware! I could have create two blog post one based on the Assessment and one on the Replication. but now you have all the details together.

Azure Migrate is there for sometime this tool makes your life easier when you want to migrate to Azure. This can migrate Vmware or Hyper-v to Azure. The process is similar as the Azure Site Recovery Process but this is only for Disaster. In the old days it is used also for migration but the Azure Migrate is much more flexible. placing VM’s on the existing network or on a different one.  New functions are released every month . https://docs.microsoft.com/en-us/azure/migrate/whats-new

For this Blog I used a Hyper-v Server and some VM’s that are migrated to an existing network in Azure. I also used 2 methods one with the Azure Migrate: Server Assessment and Azure Migrate: Server Migration  the big difference is with the Azure Migrate: Server Migration there is just a cut over no upfront assessment it creates a replica and place this in Azure.

In most of the initial migrations Customers want lift and shift. This is a method if you want to move quickly to Azure. better is to do a Server Assessment before the migration or rebuild the server on a new OS if needed.

Step 1 is in the Azure portal type Azure Migrate and check the assess and migrate.

I create a new Project for this and create a new resource group. and I choose also the geo location.

Based on hyper-V we download the Exported VM from the Azure portal and import this VM into the Hyper-v server.

select the right platform. The migration process for VMware is similar than the Hyper-V VM once the VM is connected to the portal.

We select the Hyper-v VM   in the preparation we choose to download the 9GB Migration Appliance.

When doing this on a Migration Server directly you get a warning that IE is not supported anymore.  I used Edge chromium instead. As the connections with IE failed, So a better Browser is needed.  Get Edge https://www.microsoft.com/en-us/edge?form=MA13DE&OCID=MA13DE

Importing the VM with the Hyper-v Wizard is an easy and quick step use the Hyper-v manager to import the VM

Then start the VM and the EULA is displaying and it is also the start of the migration Wizard.

Remember to use a different browser than IE. Currently IE is in the Migration server.  Get Edge https://www.microsoft.com/en-us/edge?form=MA13DE&OCID=MA13DE

We start the Migration Configuration Wizard – Remember not use IE

With the basic configuration steps we start connecting the Migration server to the Hyper-v server.

In this connection wizard we select the just created Migration project in the Azure portal. ( if you have multiple the select the right one as this is been connected to this hyper-v server)

If you have trouble to register the server Check your DNS / user account / Browser / WMI ( in a standalone site could this be an issue)

These credentials will connect to my Server. not the VM’s

You can use FQDN or the IP to connect to the Hyper-V server.

I changed the DNS to get some common errors.

Setting the DNS correctly These are common errors and often seen in standalone configurations.

This can take some time as mentioned below.

After the registration we can follow the steps in the Azure Portal.

We let this run for some time and come back later… and we move to the Database migration.

We do a different step. As the migrate tool is not showing you all the pieces

Setting up the Database Migrate. is in the same steps. but in the Azure migration blade some screens are only found in the resource groups.

Setup the Database migration project.

In this I choose the Preview option things may change when it is GA. But lets see how it works.

When this is done, I noticed that the download is not always starting https://www.microsoft.com/en-us/download/details.aspx?id=53595

When the project is created you can see the Database overview but see the real config you need to go to the resource group.

The fun part here is I created first the screenshots and add later the text but doing this I had a hard time on finding the configured items as not all components are in the migration blade. So back to the resource group there I find the hints.

The Azure Database Migration Service can be opened from the resource group as shown above.

The Discovery

When the discovery is done, then we can start with the fun part.

Here my 33 VM’s are scanned and all without an Agent.

Now that the Hyper-v Host is completely scanned we can start with the assessment of the VM’s

First we create some profiles on region and size that the VM’s will get.

This can be changed if needed

We create some Scan profiles and target location, I used the Dv4 machine types with no temp disks.

These machines are indexed and now I pick 2 for an assessment. and place them into a group

When this is ready we can see the scan results. estimated price details and the VM SKU choice

For best result you can install an agent to get more in-depth information

When the machine is not connected to an OMS workspace (Azure log analytics ) not all the info can be displayed as the service dependency’s

Add the VM to a new Workspace or to an Excising one Configure the right steps. I add a new Workspace for the Migration as this data can be removed after the migration SO I don’t want it in my current workspace.

Once the Agent is reporting to the workspace and you run a new assessment a Service map can be displayed.

Nice dashboard on the Cost and migration status, after this it is easy to migrate to Azure or you may need to do some extra work to migrate this server to Azure.

Azure Replication Migration

When Looking in the portal We can also create a Different Migration direct replication the lift and shift method. This uses the ASR tooling but with a difference here you can choose on what network the VM must land.

Installing the ASR agent on the Hyper-v Server.

Don’t forget to Finalize your registration ! this can be done after the Agent installation

Installing the ASR agent

Now that the Agent is installed we need to register this to Azure. Make sure You have downloaded the Credential file

Load the Cred file into the Agent and finishes the installation

Now we can start the Replication of the VM’s

important here to finish de registration I was forgotten this so the replication did not work.

I choose a demo VM that Can be migrated to Azure.

The Migration

Pick hyper-v or Vmware depending what you using.

I pick a VM

Selecting the resource group and Network where the VM lands. This is great now you can place the VM direct in the right spot.

My VM name is “windows” we these names are not allowed in Azure and are protected names. therefor I need to rename the VM

The replication is started and we do a Test migration.

There are no issues SO we start the test migration from the Azure blade.

Now that the failover is successful we do the cutover and run the VM in Azure. Similar as in ASR but there is no replication back.

In the Azure portal we can see the machine is running, login into the machine and check everything runs smoothly.

The VM is migrated Lift and shift. and placed on a selected network.

The replication is set to normal

Now that the VM is migrated and running we can remove this from the Hyper-v server. as the machine is not deleted on-premises.

Download this e-book to learn about Azure Migrate, Microsoft’s central hub of tools for cloud migration. In this e-book, we’ll cover:

• What is Azure Migrate
• How Azure Migrate can help your migration journey
• Running a datacenter discovery and assessment
• Migrating your infrastructure, applications, and data
• Additional learning resources

Download

Follow Me on Twitter @ClusterMVP

Follow My blog https://robertsmit.wordpress.com

Linkedin Profile Robert Smit MVP Linkedin profile

Google  : Robert Smit MVP profile