Welcome back. This is the first episode in our module three for implementing workloads and security.
And this episode we're gonna talk about as your migrate.
Our objectives include understanding what azure migrate is and how to prepare for azure migrate.
So first, what is azure? Migrate as your migrate is going to be the centralized hub to assisting with migrating your on premises Workloads, Dasher.
This hole provides a place to track discovery assessments and migration of your on premises infrastructure.
This includes tools from Microsoft as well as offerings from third party vendors. For the purposes of the course and the exam, we're only gonna focus on the tools provided by Microsoft.
This includes the server and database assessment and migration software Tools as your migrate has complete solutions to migrate your VM wear and hyper V servers, sequel databases and dot net and PHP Web APS into Azure.
One thing to note is that there have been different versions of the azure migrate tools. The previous version on Lee supported the assessment and migration of Veum wear virtual machines.
The current version supports both of'em wear and hyper V, which is an awesome improvement.
I bring this up as the examine. Questions and content may not have caught up with this. Change it.
This is the struggle with keeping exams up to date with the fast pace changes and the cloud. When I took the exam, this new version was not available in the exam. Only covered Veum wear migrations, so just remain flexible and cognizant of this one. Taking the exam.
The migration assessment involves to pulling a lightweight appliance in your data center that is used to discover and assess your on premises servers.
The discovery portion is Agent Lis, so it does not require anything to be installed on the servers to be assessed.
You can then group the service together and create migration batches.
The assessment looks at a couple of different things.
First, the readiness of the on premises servers and if they're suitable for migration, things that may make a server not suitable for migration would be older versions of operating systems that are not supported, an azure or dis sizes that are not supported, and virtual machine hardware profiles.
Understand what these limitations might be as identifying what servers are compatible for migration is an important exam topic.
Next, the assessment will recommend virtual machine sizes that compared to the actual performance of the server, it will use this data to right size your servers for a cloud deployment and help in saving compute cost
as your migrate will assign a confidence rating based on how much of the performance data it has available.
A higher confidence rating indicates the assessment feels it has a good idea of how much virtual hardware the server will need Measure.
You can also configure a comfort factor, which acts as a buffer during the assessment. This is applied on top of the performance data.
For example, say your assessment determines that two cores will work for VM, but with a comfort factor set to two X, it will sign it a four core VM hardware profile.
You can also skip the performance data recommendations and just migrate the servers, as is to azure, by configuring the sizing criteria to as on premises
in relation to sizing, be EMS, they says. It will also give a comprehensive overview of what the cost would look like if the servers were to be migrated to Azure. Finally, the assessment will take a look at any dependencies and recommend the best way to move servers and to azure.
This allows creating groups of servers to migrate and is useful if you're unsure of all the machines that make up an application and should be migrated together
at the end of the assessment, as your migrate will rate the machines on if they're ready to migrate by saying they're ready for azure conditionally ready for azure, meaning they may work but not have full support, they're not ready for azure or the readiness was unknown. Meeting there's insufficient metadata collected to make a determination.
Once the assessment is completed, it's time to migrate. The server migration tool is responsible for migrating our virtual machines from Hyper V or Veum wear into azure
in the azure portal. Under the server, migration will select the replicate option to begin replication.
Next will select the virtual machines that are ready to migrate. Then we'll select the targets for the virtual machines. Thes migrated V EMS are just like any other Veum. We build an azure. They'll need to be associated with a subscription region resource and assigned a virtual network.
Next, you'll verify Compute resource is like the hardware profile was CPU and RAM settings as well as the OS disc to boot from in any high availability settings like placing it. And in that availability set
before completing the migration, you can run a test migration to a non production azure network or just continue and finalize the migration.
Once migration is complete, be sure to follow up by changing any database connection strings or Web server configurations as well. Is updating any D. N s entries to point to the new resource is in the cloud
now? The process I just described was primarily for migrating virtual machines from Vienna. Where and hyper V.
But what if you have physical servers that you want to migrate, going from physical virtual or PTV? The configuration and steps are pretty much the same acceptable need to install a replication appliance in our on premises Data center.
This is gonna be separate from the assessment server mentioned earlier. The replication appliance requires that the mobility service be installed on each physical server.
The Mobility Service is responsible for capturing data rights on the physical server and replicating that data and the azure, the Mobility Service agent, is available for both Windows and Linux servers. Other than this additional step, migrating physical servers to azure is pretty much the same process as migrating your virtual machines.
While not explicitly listed as an exam ejected, I do want to mention some other workloads that can be migrated. The first is database migrations.
This is the ability to take on premises sequel server instances and databases into Azure Sequel database, which is a pass offering inside of Azure. The process follows the same procedures as migrating on premises servers. You create an azure migrate project and add the database assessment tool.
You'll install an appliance in your on premises data center to assess your current environment,
and it will make recommendations and detect compatibility issues that may impact the migration.
You can take a non premises database in place that into the past offering or into a sequel server instance installed on a virtual machine.
There's also the ability to migrate your Web abs. This is currently available for Web EPPS, built on dot, net and PHP. This process is quite a bit different than the process for migrating servers and databases.
There are two methods available. The first is using a public You're om point that the azure app surface can scan. This will generate a detailed report of the technology is being used and if they could be hosted on an azure APP service. If the Web app is not publicly accessible, then you can download the migration assistance to get detailed code based assessments
and walk throughs of the migration.
You can take a look at this my great toe as your APP service program by navigating to at migration that Microsoft dot com
what does it for Some of the basics of azure migrate do have, ah, follow up question. I wanted to pose
what to azure migrate Tools are used to migrate servers to the cloud.
We have the azure migrate server assessment and the azure Migrate server migration tools.
And speaking of these tools, coming up in the next episode, we're gonna go back into our azure portal and take a look at how to create an azure migrate project and some of the settings around it in our demo. See you in the next episode