Now let's double‑click into Azure Migrate Server Migration specifically.
So we're talking about themes here that are going to recur when we
look at the different Azure Migrate scenarios.
We're talking about inventory assessment,
we're talking about replication, and then ultimately a migration,
and we can do that for physical, as well as virtual machines.
The VMs can be Hyper‑V or VMware.
There are some VMware specific requirements.
You can't just have a fleet of ESX hosts,
you have to have those hosts orchestrated under vCenter,
and then your Azure Migrate appliance connects and works with the vCenter,
that's something just to keep in mind.
You can read all this in the Microsoft docs, of course.
Important point,
there is no dependency on having a virtual private network or ExpressRoute.
We're talking about TCP Port 443 with TLS SSL encryption,
and again,
remember that Azure Migrate is the successor to Azure Site Recovery
because I've mentioned this elsewhere in the AZ‑801 training when we
were learning about Azure Site Recovery.
ASR is for replication and failover, its for disaster recovery,
and you absolutely can do ASR to failover on‑premises
workloads into Azure virtual machines, but then with ASR,
you'll want to failback on‑prem, you see.
Now it used to be before Azure Migrate that we could
use or co‑opt ASR to do migration,
we would do the failover and just not re‑enable replication,
but now a much cleaner way to go and tend would be to use Azure Migrate.
I just want to give you that heads up.
Now,
if you're wondering well what's the step‑by‑step here and
how much do we have to know for the exam?
Well, you definitely need to know the step‑by‑step here.
So I've got it laid out in 6 steps.
To do an Azure Migrate Server Migration, you create a project.
You'll want to download and set up the Azure Migrate appliance,
you'll configure the appliance to run a discovery and build out an
assessment which you do in the Azure portal by providing hints.
Once you've got your assessment results,
you'll configure replication,
finalize what your Azure infrastructure will look like.
Once the storage and configuration have reached a
protected or synchronized state, you'll perform a migration,
which is a cutover to Azure, and then ongoing,
you'll verify and monitor.
So that's the bird's eye perspective.
What about migrating your old physical servers into Azure?
What do you need to keep in mind?
Well,
one thing is that Windows Server 2003 and SUSE Linux
are not supported for Azure Migrate,
so you're going to have to have as a baseline say Windows Server 2008 or later.
The assessment types,
and this isn't necessarily limited to physical server migration,
but you can specify in your assessment that you want Azure to
model and give recommendations for feature,
or performance parity rather, as in on‑premises or performance based,
The performance based is where it's more of a dynamic thing where
the Azure Migrate appliance is looking at the peaks and valleys of
the actual VM that you're inspecting, or in this case,
the physical server that you're inventorying.
Otherwise, you could just specify,
try to match how the current physical server or virtual server is set up.
It's just,
it's going to be a preference thing that you might want to test a little bit.
And then the Azure Migrate appliance is pretty much a given here
for any Azure Migrate Server Migration process,
but the Azure Migrate appliance is absolutely necessary when
you're doing physical migration to Azure,
as well as the VMware path.
Also, the physical server migration requires an agent.
There is not an agentless option here,
and you'll install that agent on the physical server that you're migrating. Let's do a demo.