Migrating Servers To Azure
Migrating a Physical Server from On-Prem to Azure with ASR
The course is part of these learning paths
With the push to the cloud accelerating, it’s critical to understand how to migrate on-prem servers to Microsoft Azure. As an IT professional, you are likely to encounter situations where you need to plan and execute such migrations.
In this course, you will learn how to evaluate migration scenarios by using Azure Migrate. We’ll cover the discovery and assessment of on-prem VMware environments and how to identify workloads that can and cannot be deployed. You’ll also learn about Azure Migrate port requirements and how to determine if the target environment is supported for a migration.
Later in the course, you will learn how to deploy and configure Azure Site Recovery (ASR) and how to use it to migrate an on-prem server to Microsoft Azure. You’ll also learn how to configure storage, create a backup vault, and how to prepare the source and target environments ahead of a migration.
The topics covered in this Azure course map very closely to learning objectives covered in the Microsoft Azure certification exams. By mastering the topics covered in this course, the student not only learns skills necessary for assessing environments for migration suitability and for performing those migrations, but the student also learns skills necessary to prepare for certification exams.
- Discover and Assess On-Prem VMware Environment
- identify Workloads that Can and Cannot be Deployed
- Identify Port Requirements
- Identify Necessary Changes to Networks
- Account Setup
Migrate Servers to Azure
- Migrate with Azure Site Recovery (ASR)
- Configure Storage and Create a Backup Vault
- Prepare Source and Target Environments
- Deploy Azure Site Recovery (ASR) Agent
- Network Preparation
- IT Professionals interested in becoming Azure cloud architects
- IT Professionals preparing for Microsoft’s Azure certification exams
- General knowledge of IT infrastructure
- General knowledge of the Azure environment
Once the target environment is configured, it's time to enable replication for the server that's going to be migrated. When you do this, site recovery will install the mobility service on the server to be migrated. After enabling replication for a server, it can take at least 15 minutes and maybe even longer for the changes to take effect and for the server to appear in the portal. To enable replication, click Replicate Application and then choose On-prem under the source. Under the Source Location, select the configuration server that you deployed earlier. In Machine Type, select Virtual Machine. Select the process server to use for the replication. In a default configuration, this will typically be the configuration server that you deployed. Click OK to continue.
In Target, select the subscription and the resource group where the Azure VM should be created after failover and choose the deployment model that you want to use in Azure. In our case and in most cases, choose Resource Manager. Select the Azure storage account to use for replicating data, and choose the Azure virtual network and subnet to which the Azure VM will connect when it's failed over. Select Configure Now to apply the network settings to all protected machines. Selecting Configure Later allows you to select the Azure network on a per-machine basis. In our case, we're only migrating one machine, so the point is really moot. Click OK to continue configuration. Under Virtual Machines, select the virtual machine you wish to migrate, and then click OK.
In our case here, we're migrating Server01. In Configure Properties, select the account that will be used by the process server to automatically install the mobility service on the machine being protected and click OK. In our case here, we're using Administrator which we set up previously, and this will allow access to our virtual machines to actually install the mobility service. In Replication Settings, verify that the correct replication policy is selected. If you need application consistency across multiple servers, select Yes under Multi-VM Consistency so you can create a replication group. In our case, we are replicating and migrating just one VM, so we can leave it set to No. Click OK to continue, and to turn on replication, click Enable Replication. You can track the progress of the replication by clicking Replicated Items under Protected Items in the left pane. Clicking the server name provides further details on the replication status. Obviously, you need to ensure the server's fully replicated before trying to migrate it. Once the machine is 100% synchronized, it's ready for failover. The time it takes for a machine to become 100% synchronized to Microsoft Azure is largely dependent on the bandwidth from the source location to Azure.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.