Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Migrate machines as physical servers to Azure
In this articleThis article shows you how to migrate machines as physical servers to Azure, using the Migration and modernization tool. Migrating machines by treating them as physical servers is useful in a number of scenarios:
This tutorial is the third in a series that demonstrates how to assess and migrate physical servers to Azure. In this tutorial, you learn how to:
Note Tutorials show you the simplest deployment path for a scenario so that you can quickly set up a proof-of-concept. Tutorials use default options where possible, and don't show all possible settings and paths. For detailed instructions, review the How-tos for Azure Migrate. If you don't have an Azure subscription, create a free account before you begin. PrerequisitesBefore you begin this tutorial, you should:
Prepare AzurePrepare Azure for migration with the Migration and modernization tool.
Assign permissions to create project
Assign Azure account permissionsAssign the Virtual Machine Contributor role to the Azure account. This provides permissions to:
Create an Azure networkImportant Virtual Networks (VNets) are a regional service, so make sure you create your VNet in the desired target Azure Region. For example: if you are planning on replicating and migrating Virtual Machines from your on-premises environment to the East US Azure Region, then your target VNet must be created in the East US Region. To connect VNets in different regions refer to the Virtual network peering guide. Set up an Azure virtual network (VNet). When you replicate to Azure, Azure VMs are created and joined to the Azure VNet that you specify when you set up migration. Prepare for migrationTo prepare for physical server migration, you need to verify the physical server settings, and prepare to deploy a replication appliance. Check machine requirements for migrationMake sure machines comply with requirements for migration to Azure. Note When migrating physical machines, the Migration and modernization tool uses the same replication architecture as agent-based disaster recovery in the Azure Site Recovery service, and some components share the same code base. Some content might link to Site Recovery documentation.
Prepare a machine for the replication applianceThe Migration and modernization tool uses a replication appliance to replicate machines to Azure. The replication appliance runs the following components.
Prepare for appliance deployment as follows:
Note The replication appliance shouldn't be installed on a source machine that you want to replicate or on the Azure Migrate discovery and assessment appliance you may have installed before. Set up the replication applianceThe first step of migration is to set up the replication appliance. To set up the appliance for physical server migration, you download the installer file for the appliance, and then run it on the machine you prepared. After installing the appliance, you register it with the Migration and modernization tool. Download the replication appliance installer
It may take some time after finalizing registration until discovered machines appear in the Migration and modernization tool. As VMs are discovered, the Discovered servers count rises. Install the Mobility serviceOn machines you want to migrate, you need to install the Mobility service agent. The agent installers are available on the replication appliance. You find the right installer, and install the agent on each machine you want to migrate. Do this as follows:
Note In the /Platform parameter, you specify VMware if you migrate VMware VMs, or physical machines. Install on Windows
Install on Linux
Replicate machinesNow, select machines for migration. Note You can replicate up to 10 machines together. If you need to replicate more, then replicate them simultaneously in batches of 10.
Note To replicate VMs with CMK, you'll need to create a disk encryption set under the target Resource Group. A disk encryption set object maps Managed Disks to a Key Vault that contains the CMK to use for SSE.
Note You can update replication settings any time before replication starts, Manage > Replicating machines. Settings can't be changed after replication starts. Track and monitor
You can track job status in the portal notifications. You can monitor replication status by clicking on Replicating servers in Migration and modernization. Run a test migrationWhen delta replication begins, you can run a test migration for the VMs, before running a full migration to Azure. We highly recommend that you do this at least once for each machine, before you migrate it.
Do a test migration as follows:
Migrate VMsAfter you've verified that the test migration works as expected, you can migrate the on-premises machines.
Complete the migration
Post-migration best practices
Next stepsInvestigate the cloud migration journey in the Azure Cloud Adoption Framework. FeedbackSubmit and view feedback for Additional resourcesAdditional resourcesIn this articleWhat is Azure migrate server migration?Azure Migrate provides a simplified migration, modernization, and optimization service for Azure. All pre-migration steps such as discovery, assessments, and right-sizing of on-premises resources are included for infrastructure, data, and applications.
When planning to migrate a public website to Azure company must to plan?When planning to migrate a public website to Azure, you must plan to pay monthly usage costs.
When planning to migrate a public website to Azure you must plan to pay monthly uses cost?Azure Migrate: Server migration is free for first 180 days for each machine. After 180 days, $25/month per instance replicated will be applied.
Which tools can be used to migrate to Azure after performing an assessment in Azure migrate?You can use the Azure Migrate Discovery and assessment tool to create assessments for on-premises VMware VMs and Hyper-V VMs, in preparation for migration to Azure. The Discovery and assessment tool assesses on-premises servers for migration to Azure IaaS virtual machines and Azure VMware Solution (AVS).
|