>> Hello and welcome. My name is Abhishek Hemrajani.
In this video, I'll walk you through the process of
large-scale migration of Hyper-V VMs
to Azure with Azure migrates
civil assessment and civil migration capabilities.
But before we start,
here are two videos that I recommend you watch first.
Watch the Get Started with Azure Migrate video to
learn about the new Azure Migrate hub experience.
Azure Migrate is now a hub for all your migration needs and tools.
In that Get Started video,
I walk you through the process of
creating a new Azure Migrate project and instantiating
the server assessment and server migration tools.
In the second video, I walk you through
the process of discovering, assessing,
and migrating VMWare Virtual Machines
using the new integrated experiences in Azure Migrate.
In this video, we will talk about Hyper-V,
but most of that functionality is already covered
in the VMWare video. Let's get started.
So here I am on the Azure Migrate portal experience.
Start by clicking on "Syllabus".
That should bring you into your existing Azure Migrate project.
In my previous video,
I had created the Contoso project and had
discovered my VMWare Virtual Machines into that project.
I'll start off by clicking "Discover" on server assessment.
This time, I'll select Hyper-V as the virtualization platform.
I now get the option of downloading
the Azure Migrate appliance in a VHD format.
I'll download that appliance,
bring up a Virtual Machine using the VHD,
and I'll be able to get started
with Azure Migrate server assessment
for Hyper-V. Just as you do with VMWare,
once the Azure Migrate appliance is up and running,
you get presented with the default configuration experience.
In short, that prerequisites are in place.
A detailed prerequisite guide with
a prerequisite checklist and scripts to help you
get started is available in the documentation.
I strongly recommend you review that before you get started.
It looks like my appliance has
everything that's needed to get started.
I simply click on "Continue".
At this depth, I'm going to login to my Azure subscription.
Once I'm logged in,
I'm able to select my demo subscription,
I'll "Select" the same Contoso project that I've
been using and I'll give this appliance a name.
For ease of management,
I'm going to call this appliance HyperV1.
Click on "Register" to register the appliance
with the Azure Migrate server assessment service.
Once the registration is successful,
click on "Continue" to provide
the Hyper-V source environment details.
Before you can initiate discovery on
your Hyper-V host or clusters,
you'll need to provide the username and
password to those source environments.
Once the credentials had been saved,
click on "Add" to provide a list of
your Hyper-V hosts or Hyper-V clusters.
As a final step, hit "Validate".
This will ensure that your hosts are reachable
and accessible via the credentials that you've provided.
Once the validation is complete,
you get an output with an information of
the number of Virtual Machines on every single host.
I have roughly 3,000 Virtual Machines
across 75 hosts in this validation output.
I recommend discovering between
5,000-6,000 Virtual Machines for Hyper-V appliance.
You can bring discovery information from multiple appliances into
the same Azure Migrate project and perform
large-scale assessments for Hyper-V just as we did for VMWare.
As a final step,
click on "Save as doc Discovery".
Once the discovery is complete,
the discovered server count on
my Azure Migrate server assessment will get updated.
I can also click on "Overview" to view the inventory.
I can choose to perform assessment for all my Virtual Machines at
the same time or I can choose to
perform assessments at an application level.
For this video, I'm going to go ahead and create an assessment for
my Contoso HR app which is made up of four Virtual Machines.
In the VMWare discovery assessment and migration video,
we saw the process of creating an assessment on top
of all Virtual Machines discovered from a datacenter.
Let's go ahead and get started with
an application level assessment this time.
Click on "Assess".
Let's start by giving this assessment a name.
I'm going to call it ContosoHR.
Let's also go ahead and create a group for our Virtual Machines.
I'm going to call that group ContosoHR as well.
I'll select all the Virtual Machines that
are participating in my application.
The assessment will get computed
using the default assessment properties.
To modify the assessment properties,
click on "View All".
The Azure Migrate documentation provides
comprehensive listing of these settings.
You can also modify settings,
post the creation of an assessment.
For now, I'm going to stick with the defaults.
To finish the process,
click on "Create assessment".
Once the assessment has been computed,
you can review the Azure readiness information and
the cost details for every machine in your application.
You can also use the view dependencies feature to visualize
dependencies before you start your migration process.
Now that I have verified all of the information related to
discovery and assessment of my Hyper-V based application,
I'm ready to start performing migration.
Click on "Azure Migrate Servers".
That should bring you back in
the servers expedience of Azure Migrate.
To get started with migrating
your Hyper-V Virtual Machines, click on "Discover",
select the target region that you plan to perform migrations to,
and click on "Create resources".
For both VMWare and Hyper-V,
you do not need any agents on
your Virtual Machines to perform migrations to Azure.
The only differences in the case of Hyper-V,
you need to complete two steps on
your Hyper-V host before you can start replicating servers.
Follow the instructions on the discovered machines blade.
Once you've completed the instructions,
you're ready to start replicating your applications to Azure.
Simply click on "Replicate"
select "Hyper-V" as the virtualization platform,
click "Next" to select
the Virtual Machines that you want to replicate.
With end-to-end integration, the assessment information from
your existing Azure Migrate assessment can
automatically be applied to the VMs as they're migrated to Azure.
Simply click on "Yes" to apply
migration settings from an existing Azure Migrate assessment.
You can then select your group.
I had created a group ContosoHR for
my Hyper-V Virtual Machines and then
select an assessment that you want to use for the migration.
This will automatically pull up
the Virtual Machines that are part of that application.
Click "Next" to specify the target settings for your application.
You can specify the subscription, the resource group,
storage account, and network information for
your Virtual Machines as you migrate them to Azure.
You can also benefit from the Azure hybrid benefit offer
if you have Windows Server licenses covered by Software Assurance.
Click " Next" to confirm the compute and disk recommendation.
You'll notice that the assessment information has already
been applied to the compute information for the Virtual Machines.
As a final step,
review the information and click
"Replicate" to start the replication process.
The latest information gets updated in
these server migration tile on Azure Migrate.
I can see that my servers have replicated successfully.
I can take quick actions such as migrating those servers to Azure.
I can also click on "Overview" to see things in better detail.
I can see that I have 13 servers replicating to Azure.
I can perform a test migration on my application.
This will ensure that an isolated copy of
my Contoso HR app gets created in Azure so
that I can validate the performance of
the right-sized app before deciding to migrate it to Azure.
When performing migration, I get the option of performing
a blank activity which
includes a zero data loss migration to Azure.
It's as simple as that.
So that's what I had for you in this video.
We saw how easy it is to get started with
Azure Migrate server assessment and server migration capability.
We were able to create
large-scale assessments for our entire Hyper-V datacenter.
We also created an assessment for the Contoso HR app.
The assessment gave us
comprehensive information related to the readiness
and cost details before we
decide to perform the migration to Azure.
Once you are happy with the assessment,
we were able to start replicating
those Hyper-V Virtual Machines using
the integrated server migration experience.
All of our assessment details were automatically applied
to the VMs before they start replicating to Azure.
Throughout the process, the information keeps getting
updated on the server migration tile in Azure Migrate.
Finally, test migration gives you the option to validate
the performance of your right-size
app before you decide to migrate it to Azure.
I hope you found the content useful.
Thank you and keep watching.