Douglas Francis: Well, today we're going to talk
about how to leverage Azure Migrate to assess and
migrate workloads. You might be running that in
your on premises data center up into the Azure as
eyes. Get started as your migrate users go into
the Azure portal and actually create an Azure
migrate solution, resource. Search manager migrate
and select that. Go ahead and to this option right
here and click create.
By default, you'll see thisin started dashboard
when you sign on. It was a couple things into for
discover, assess and migrate servers. This was
looking at taking your on premises virtual
machines and migrating them to Azure IS assessed
and migrate databases covered during your
traditional database workloads into sequel pass
and there's also information for data box, which
is essentially Microsoft sending you a drive, you
copy your data over to it, ship it back. And then
they can put into a storage account in Azure,
which depending on the cost of your network links
and how much data you have could actually be,
which could be a more cost effective and efficient
solution for migrating large amounts of data up
into Azure.
Or focus on here is migration of servers. So we're
gonna go ahead and check out the migration goals
servers. By default, you won't have anything in
here, but set for links to add assessment tools,
but I've already got some stuff prepped out for
this. What you're going to have for assessment
tools are several options of Microsoft option. And
there's these handful other ones from the third
party marketplace. If you already have something,
for example, like turbonomics that you've been
using on prem to analyze your workloads, then you
can go ahead and use turbonomics. Again to analyze
what workloads into Azure. What we're going to
focus on here is the Microsoft one.
To start with Azure migrate. First you need to
assess what your environments like
so if you click the discover button,
you're gonna get this pop up, can ask you do you
want, if your machines are virtualized on Vsphere
or with Hyper V, then you can go ahead and select
the appropriate version, what you need to do is
grab the OVAVHD and deploy those to either ESX or
Hyper V.
It's a little bit outside the scope of this, but
fairly simple process, download those, install
them. Once you install those, bring those online
they'll automatically start the wizard. That was
just got a few things that you need to set up on
that VM here, setup pre recs, mostly in case of
like ESX, there is a SDK that you need to download
install. It gives you a link to that when you need
it. So it's fairly easy to grab your duty VMware
account for that. When you sign into the Azure
portal on here, make sure that you're signed in to
the correct address, subscription and tenant. Once
a assessment VM is tied to a subscription, it
cannot be changed. If you want to change you'd
have to redeploy that LPA. You're then going to
authenticate to in this case of the V center. V
center, it needs potentials to read data that's in
the cluster. If you lose a limited scope account,
then there would be a limited scope of what the
assessment can pick up. So if you actually want to
do a true assessment of everything in the data
center, then you need to provide an account that
has everything, has read access to everything, to
actually look and see it. Once you go ahead and
set all that up, it'll initiate a discovery based
about 10, 15 minutes for the engine to actually
look at your information, look at your cluster and
then start showing off of the portal. So after
about here, that 15/20 minute period, you'll see
some information and discovered servers, and go
and check that out. So this will be the service
that whatever that credentials have access to.
Real quick, you'll see that there are dependencies
here that requires agent installation.
If you want to have a very full in depth analysis
of what your dependencies on your workloads, you
can go ahead and install the Microsoft monitoring
agent on your VM. This will actually use on OMS
workspace to determine, based upon everything that
is going through that box, what other boxes of
stock into? So you can validate that, Oh yes,
application server one is actually talking
application server two, three, and then the nice
of the databases. And actually get a full
dependent map on what those services are talking
to. So you can have a very good understanding that
when you get ready to migrate something as you
that you're migrating the entire solution in. Or
you know what all your dependencies are backed on
prem resources, rather than a best guess kind of
scenario. This is not required at all, there's a
bit additional cost for having that OMS workspace
and a bit of extra effort installing the agent,
but is a very nice thing to consider, especially
if you have very large complex workloads. At this
point, we're just gonna go on a quick and easy so
looking at this, it's going to give you the name,
IP address, and then specs on the machines that
you have enabled.
What you need to do then is go ahead and create an
assessment. Assessments are how you're going to
determine what you have on prem and then what
that's going to look like in terms of going into
Azure. MC this assessment property, you really
need to come in here and actually view all the
settings, first your target location, I'm going to
go ahead and sent this to South Central US, one
of the closer datacenter regions to me.
I'm an automatic storage type, I'm
going to go ahead and leave this set to automatic,
you can change how this goes later if you have the
need to, which is better idea than just telling
that you actually need premium this maybe then you
actually don't. Next thing up is reserved
instances. It is possible to buy virtual machines
all at once for a one year or three year period
and you get a significant discount on that. I
think in terms of actually playing out what the
assessments going to do and the cost that's going
to be associated with it, you should have a no
reserved instances, you'd rather have a worst case
scenario or cost criteria than having maybe a
reserved instance on here for a three year getting
that discount and then either end up overpaying
for a year of services or not using th
Next with the VM sizing criteria. You got
performance based and you have as on premise
space, if you do as on purposes, it's going to go
ahead and actually change some of your settings
away for you if you don't have the ability to kind
of look at that, this will be as close as it can
be in terms of what is on prem into what is
available. And Azure, for example, you have a
three court VM and Azure. So if you have one of
those on prem, then you're not going to get one of
those in Azure. So it's going to be upsized to
wherever the next closest thing is, I highly
recommend doing a performance based configuration
off and a lot of virtual machines on prem are
oversized, and you don't want to be wasting that
cost resources in Azure if you don't need it. So I
would also recommend you have options. Look at
performance history for one day, one weekend, one
month. The longer, you're able to let this sit
there analyze the environment that it's running
in, the better idea you're going to get. There
will also be a confidence rating later that will
be impacted by how long you're looking at this.
Migrating in Azure isn't something you're
generally going to do over one night. So we're
going to sit there for, you know, a month and
actually understanding what that workload is like
it peaks and valleys and servers is a pretty good
idea. I also prefer set the comfort factor up to
1.2. I like a little bit of fudge room in there.
Now I might not necessarily actually go with that
at the end of the day but I liked having that
little bit of room in there just to kind of think
about. And then also for my VM series, I suggest
taking a selecting all of these, you have an idea
that you only want general purpose VM and you
don't want memory optimized, you don't want
compute, optimize, go ahead and run remove those,
I think have a general purpose. And there's a
pretty good idea just so you can get an idea of
what your workloads might look like and what the
assessment instrument makes, those might be going
down and pricing. The offer box has a ton of
things in there pays you go depth tests as your
past options, lots of options and about ways you
can consume as your pay as you go is pretty good
for just a flat base.
You also see a discount, it's possible to have a
discount on Azure services based upon commitments
with your enterprise agreement. If you have that
as a guaranteed thing, you know what that is. Feel
free to put that in. Once again, though, unless
you know that's a guaranteed thing. I will leave
this as to ensure that you're getting the possible
worst outcome. Final thing to point out is it says
already have a Windows Server license. This is on
by default. If you do not have a eligible server
license that has hybrid benefit, then that's going
to be a bit of a sticker shock through. That's a
45% increase in pricing from hybrid benefits. So
buckle your account team in your licensing expert
Unknown: So, we're going to go ahead and do that.
and determine if you do have hybrid licensing that
will save you a bit of money instead of having to
pay for the licensing costs with the virtual
machine, but you got to be very careful, ensure
that you're aware of that. I'm gonna go ahead and
click Save. Now, you can put everything in a group
for the first two steps and I think you should
have at least one assessment It has everything in
it. That way you just get a good idea and if you
just took this entire ESX cluster, the entire
Hyper V cluster stuck in an Azure IS, how muc
would it cost you
Douglas Francis: Right now let's go look at that
assessment that we have. You'll see I got some
assessments here, already. Pull up this one real
quick.
Real quick, you have some information here. So how
many virtual machines I have that are absolutely
ready to migrate to Azure army that are has some
conditions and and maybe some issues, also them
estimated costs on compute and storage. So you'll
see that I have one being that's ready to go
although that have some conditions that might need
to be fixed. It'd be $1500 for compute then $184 a
month on storage costs, gives you a good breakdown
on what that's gonna look like. I'm actually
digging into the readiness of this. Generally,
what you're going to see is you're gonna see ready
with conditions for anything that's running a EFI
boot mode on Azure, as of right now, has not had
EFI boot mode support. So this would actually need
to convert this VM to BIOS boot as part of the
conversion process which can be a thing. So that's
actually not that big of a concern to worry about.
Now, if we look at the assessment, so everything
run down, it will give you a Hey, this is unknown.
A case of that PF some spots right there that says
unendorse Linux distro. That's previous D. So that
makes sense. So kind of give you an idea on me
just there, what the storage target and I give you
a good, all set of what that's going to look like.
And it's also going to tell you what VM it thinks
it should be soon, you know, in the case of that
DC right there things such as standard A1D2 will
be good enough to support that workload based upon
what the assessments right investment, actually
dig into the properties of a virtual machine. Once
again, you'll have that kind of high level
overview, give you a head, you want to you can do
a migration with Azure migrate.
Based upon currently it's using two cores only
using 11% of that it's got full four gigs of RAM
only using 19% of that is your an idea of what
that utilization workload is in terms of operation
usage, give you a nice idea. So you can go through
and then you can have multiple assessments,
multiple assessments can be part of any
environment. You'll see I have multiple here. Look
at this one, it says out of sync, and that's
because I've actually added or removed to group to
as part of the testing so it'll give you an idea
if something's out of date.
On the cost details thing, we'll just basically
break down that overview of what you saw earlier,
how much that's going to cost in terms of each VM,
or compute and/or storage unit. It is an estimate,
but you want to escalate that up and calculate as
well. If you think that something's wrong, you can
always use the public Azure pricing calculator and
kind of think about things as well. So once you
have assessed your environment, you kind of have
an idea of what you're going to move to and how
much it's going to cost. It comes with actual
migration face. Now here we have the migration
tools, I already have one enabled, or also just
like in the assessment tools, other options on
this urbanite and cortex though, they provide some
information here.
What's nice about them is they have virtual
machine support as well. Alright, so we're going
here, we've got discover servers, two servers that
are replicating. We've got a test migration and
then we have a migrated server. But let's look at
the replicating phase one first on this. actually
use Is as your site recovery in the backend to
replicate servers. It's going to ask you, are we
virtualized? So yes, going to select the appliance
that we've put in.
If you want to take the information from the
assessment you already have you can do that will
just take this group, take that assessment, we
could take this and we go ahead and migrate all of
that all one quick jump, we're just going to do
one real quick. Just kind of get an idea what this
looks like. Think this DC here. Alright, so we're
going to select our subscription and our resource
group are going to select a virtual network and a
subnet that we're going to put that on that
automatically go on a sudden that if you don't
have it, it'll once again tell us about as your
hybrid benefit.
The compute's going to give us some information so
automatically based on size and config, if you
disagree with what that sizing and config was you
come in here manually select me basically one and
it would deploy that. Were gonna go and set that
back to automatically select go next. Like I said
earlier, the standard SSD will be good enough for
some things. Other things you may I, if the
virtual machine you select doesn't have that tier,
if you select them premium one, then you might
actually not see all those options. And then
you're going to go ahead and then just hit the
replicate button, I've already got one
replicating. So we're going to go take a look at
that. So a couple things are good. So you'll see
that I have two that are in a healthy state, and
then one that has already been migrated. When you
actually hit replicate something might take a
while for it to become a healthy state. All of
these at one point were in unhealthy states, I
didn't know troubleshooting to them. I just let
them sit and kind of turn and after an hour or
two, they weren't healthy and started migrating.
Looking at this app server here, it's currently
Delta sync face. What this means is it's an
initial replication and it's done submit for
information there. You'll see here there's been
some failures here. It's all good once as long as
keeps up, we're fine. I have the option to come in
here and do a stop replication, I have option to
do a secret ization, cleanup migration and do a
test migration. And this one has already performed
a test, which is why it's in a clean up test
migration state. All a test does is it actually
takes a does it count as a Delta sync of that
data, charges create in turns on a VM and Azure,
you can actually sign in that VM and Azure and
test it out in a limited amount, right, it's going
to be on a different networking segment and veal
and in Azure, but you could turn that on test out,
make sure it kind of works a little bit, and then
clean up that test migration when you're done. And
then can have that good test policy to make sure
it even boots and comes online with the way you
expected.
Once you actually do a migration path, it's going
to go ahead and actually turn off the virtual
machine on prem and do a Delta sync and ensure
that it has every bit of data and nothing's going
to change after that completion and then sync that
data into Azure, our vM on and then you're good to
go and change your DNS settings and make sure your
connection works in that server, provide whatever
features that was. This is something you're going
to do during a maintenance window, it may take a
couple hours between DNS propagation and delta
sinks and your network bandwidth to actually go
from shut down, full Delta, sync any changes,
employment and turn on a VM. So it's not something
you're gonna do in a few minutes during the middle
of the day, but somebody can plan them into
evening. And get that moved in up there pretty
quickly. The biggest thing with Azure migration is
ensuring that everything is done planned out from
a dependency point of view of your networking
segments put in. So it's really good to do that
testing and make sure that servers can talk back
and forth between our primary sources you have
them at the latencies Okay, and do that actual
network testing. As long as you do your planning
assessment and you have an idea of what your scale
sizes into your network connectivity to your
network connectivity is good. The migration part
itself sparely is a good process to kind of do a
lift and shift to those services in Agile.
Right Well, I hope you found useful information
and how to migrate into Azure and I wish you good
luck on your migration efforts.