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 collector has been deployed, it's time to discover virtual machines. To do so, open the vSphere Client console and connect to the newly deployed collector VM. Accept the licensing terms and provide a password. Next, log into the deployed VM and ensure the time zone and time are correct. You should also confirm that the IP address, server name, and typical server deployment details are accurate and correct. Once this is done browse through the desktop and click the Run Collector shortcut. The collector will check that the VM has internet access and then checks that the collector service is running. This service is installed by default on the collector VM. It will download and install VMware Power CLI. When prompted to specify vCenter Server details specify the FQDN or IP address of the vCenter Server, and in the username and password fields, specify the read only account credentials that the collector will use to discover VMs on the vCenter Server.
Notice that it shows a warning that utilization-based recommendations may not work as expected because statistics collection on the vCenter Server isn't yet set to level three. To ensure Azure Migrate can make utilization-based recommendations be sure to set statistic collection to level three by switching over to vSphere, clicking Administration, and then browsing to the vSphere settings option. Set the level to three for all statistics intervals. You should then wait at least a day, preferably a month, before running the first collection. This is done to ensure utilization-based recommendations are accurate for all intervals. Otherwise, as the notification indicated, the recommendations that Azure Migrate makes will simply be based on the hardware specs of the VM being discovered.
In collection scope select a scope for VM discovery. The collector can only discover VMs within the specified scope. Scope could be set to a specific folder, data center, or cluster, but it shouldn't contain more than 1500 VMs. In specify migration project, specify the Azure Migrate project ID and key from the portal. To get them open the Azure portal, browse to the migration project overview page and click discover. From here you can copy these values. In view collection progress, monitor discovery, and check that metadata collected from the VMs is in scope.
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.