Shulou(Shulou.com)06/03 Report--

AzureMigrate discovers the enterprise's internal deployment environment through device-based agentless discovery, from VMware virtualized Windows and LinuxVM to applications and data. This article will introduce Azure Migrate devices. Devices can be deployed when using the Azure Migrate: server evaluation tool to discover and evaluate applications, infrastructure, and workloads to be migrated to Microsoft Azure. When migrating VMware Vm to Azure, you can also use Azure Migrate: migrate VMware vm to Azure using an agentless migration server evaluation. 1. Overview of equipment

Use Azure Migrate devices in the following scenarios.

Scenario tool for VMware VMAzure Migrate: server evaluation

Azure Migrate: server migration discovery VMware Vm

Discover computer applications and dependencies

Collect computer metadata and performance metadata for evaluation.

Replication VMware Vm and agentless migration. Hyper-V VMAzure Migrate: server evaluation found Hyper-v Vm

Collect computer metadata and performance metadata for evaluation. Physical machine Azure Migrate: server evaluation discovers physical server

Collect computer metadata and performance metadata for evaluation. 1) device-VMware requires VMware download format... Ova download link https://aka.ms/migrate/appliance/vmware download size 11.2 GB license downloaded device template comes with a Windows Server 2016 Evaluation license, which is valid for 180 days. If the evaluation period is nearing expiration, we recommend that you download and deploy the new device, or activate the operating system license for the device VM. Deployment deploys the device as VMware VM. Sufficient resources are required on the VCenter Server to allocate VM with 32 GB RAM, 8 vcpu, disk storage of approximately 80 GB, and external virtual switches.

The device needs to access the internet directly or through an agent.

The device can be connected to a single vCenter Server. Resources on the hardware VCenter to allocate VM with 32 GB RAM and 8 vcpu, disk storage of approximately 80 GB, and external virtual switches. Hash algorithm hash value MD5c06ac2a2c0f870d3b274a0b7a73b78b1SHA2564ce4faa3a78189a09a26bfa5b817c7afcf5b555eb46999c2fad9d2ebc808540cvCenter server / host device VM must be deployed on ESXi hosts running version 5.5 or later.

Run 5.5,6.0,6.5 or 6.7 vCenter Server. Azure Migrate project devices can be associated with a single project.

You can associate any number of devices with a single project.

Discovery devices can find up to 10000 VMware Vm on the vCenter Server.

The device can be connected to a single vCenter Server. Device component management application: a Web application in a device entered by the user during deployment.

Discovery Agent: collects computer configuration data.

Evaluation agent: collects performance data.

DRA: coordinate VM replication and coordinate communication between computers / Azure.

Gateway: sends replicated data to Azure.

Automatic update service: update components (run every 24 hours). VDDK (agentless Migration) if you run an agentless migration in the case of an Azure Migrate server migration, you must install VMware vSphere VDDK on the device VM. 2) device-Hyper-v requires Hyper-V download format compressed folder (including VHD) download link https://aka.ms/migrate/appliance/hyperv download size 10 GB license download the device template comes with the Windows Server 2016 Evaluation license, which is valid for 180 days. If the evaluation period is nearing expiration, we recommend that you download and deploy the new device, or activate the operating system license for the device VM. Device deployment deploys the device as Hyper-v VM.

The device VM provided by Azure Migrate is Hyper-v VM version 5.0.

The Hyper-v host must be running Windows Server 2012 R2 or later.

The host needs enough space to allocate 16 GB RAM, 8 vcpu, approximately 80 GB of storage, and an external switch for the device VM.

The device requires a static or dynamic IP address and internet access. Resources on the hardware Hyper-v host to allocate 16 GB RAM, 8 vcpu, approximately 80 GB of storage space, and external switches for the device VM. Hash algorithm Hash value the MD529a7531f32bcf69f32d964fa5ae950bcSHA25637b3f27bc44f475872e355f04fcb8f38606c84534c117d1609f2d12444569b31Hyper-V host is running Windows Server 2012 R2 or later. Azure Migrate project devices can be associated with a single project.

You can associate any number of devices with a single project.

A maximum of 5000 Hyper-v Vm can be found per device.

A device can connect to up to 300 Hyper-v hosts. Device component management application: a Web application in a device entered by the user during deployment.

Discovery Agent: collects computer configuration data.

Evaluation agent: collects performance data.

Automatic update service: update components (run every 24 hours). 3) device-physical download format requires a compressed folder (containing PowerShell-based installer scripts) download link https://go.microsoft.com/fwlink/?linkid=2105112 download size 59.7 MB hardware dedicated physical computer, or use a virtual machine. The computer running the device requires 16 GB RAM, 8 vcpu, approximately 80 GB of storage space, and an external switch.

The device requires a static or dynamic IP address and internet access. Hash algorithm Hash value MD51e92ede3e87c03bd148e56a708cdd33fSHA256a3fa78edc8ff8aff9ab5ae66be1b64e66de7b9f475b6542beef114b20bfdac3c operating system device computer should be running Windows Server 2016. The device deployment device installer script is downloaded from the portal (in a compressed folder).

Extract the folder and run the PowerShell script (AzureMigrateInstaller). A maximum of 250 physical servers can be found for one device. Device component management application: a Web application in a device entered by the user during deployment.

Discovery Agent: collects computer configuration data.

Evaluation agent: collects performance data.

Automatic update service: update components (run every 24 hours). 4) URL access requirements

The Azure Migrate device needs to be connected to the internet.

When you deploy the device, Azure Migrate checks the connectivity of the Url summarized in the following table. If you use URL-based agents to connect to the internet, allow access to these Url, ensuring that the agent parses any CNAME records received when looking up the Url. URL details * .portal.azure.com navigate to the Azure portal. * .windows.net

* .msftauth.net

* .msauth.net

* .microsoft.com

Log in to Azure subscription for * .live.com. * .microsoftonline.com

* .microsoftonline-p.com creates an Active Directory application for the device to communicate with Azure Migrate. Management.azure.com creates an Active Directory application for the device to communicate with the Azure Migrate service. Dc.services.visualstudio.com uploads application logs for internal monitoring. * .vault.azure.net manages secrets in Azure Key Vault. Aka.ms/* allows access called "links". Used for Azure Migrate device updates. Download.microsoft.com/download allows downloads from Microsoft. Communication between the .servicebus.windows.net device and the Azure Migrate service. * .discoverysrv.windowsazure.com

* .migration.windowsazure.com connects to the Azure Migrate service Url. * .hypervrecoverymanager.winwinazure.com for VMware agentless migration

Connect to the Azure Migrate service Url. * .blob.core.windows.net for VMware agentless migration

Upload data to storage for migration. 2, the device collects metadata after the Azure Migrate device deployment will find some data and use it to help you resize the application appropriately when migrating the application to Azure, performing Azure applicability analysis, application dependency analysis and cost planning. Microsoft will not use this data relative to any license compatibility review. 1) below VMware is the VMware VM performance data collected by the device and sent to Azure. Data counter evaluation affects CPU usage cpu.usage.average recommended VM size / cost memory utilization mem.usage.average recommended VM size / cost disk read throughput (MB/ seconds) virtualDisk.read.average disk size, storage cost, VM size calculation disk write throughput (MB/ seconds) virtualDisk.write.average disk size, storage cost, VM size calculation disk read operations per second virtualDisk.numberReadAveraged.average disk size, Calculation of storage cost, VM size, disk write operations / second virtualDisk.numberWriteAveraged.average disk size, storage cost, VM size calculation NIC read throughput (MB/ seconds) net.received.averageVM size calculation NIC write throughput (MB/ seconds) calculation of net.transmitted.averageVM size

The following is a complete list of VMware VM metadata collected by the device and sent to Azure.

Data counter computer details VM IDvm.Config.InstanceUuidVM name vm.Config.NamevCenter Server IDVMwareClient.Instance.UuidVM description vm.Summary.Config.Annotation license product name vm.Client.ServiceContent.About.LicenseProductName operating system type vm.SummaryConfig.GuestFullName startup type vm.Config.Firmware kernel number of memory (MB) number of vm.Config.Hardware.MemoryMB disks vm.Config.Hardware.Device.ToList () .FindAll (x = > is VirtualDisk ) .count disk size list vm.Config.Hardware.Device.ToList () .FindAll (x = > is VirtualDisk) network adapter list vm.Config.Hardware.Device.ToList () .FindAll (x = > is VirtualEthernet) .countCPU utilization cpu.usage.average memory utilization mem.usage.average per disk details disk key value disk.KeyDikunit number disk.UnitNumber disk controller key value disk.ControllerKey.Value preconfigured quantity (GB) virtualDisk.DeviceInfo.Summary disk name uses disk.UnitNumber Disk.Key Disk.ControllerKey.VAlue generated value read operations per second virtualDisk.numberReadAveraged.average read operations per second virtualDisk.numberWriteAveraged.average read throughput (MB/ seconds) virtualDisk.read.average write throughput (MB/ seconds) virtualDisk.write.average per NIC detailed message network adapter name nic.KeyMAC address ((VirtualEthernetCard) nic). MacAddressIPv4 address vm.Guest.NetIPv6 address vm.Guest.Net read throughput (MB/ seconds) net.received.average write Throughput (MB/ seconds) net.transmitted.average inventory path detail name container.GetType (). Name sub-object type container.ChildType reference details container.MoRef parent details Container.Parent folder details per VM ((Folder) container) .ChildEntity.Type data center details per VM ((Datacenter) container) .VmFolder data center details per host folder ((Datacenter) container). HostFolder Cluster details of each host ((ClusterComputeResource) container) .Host host details of each VM ((HostSystem) container) .VM

2) Hyper-V

The following is the Hyper-V VM performance data collected by the device and sent to Azure.

Performance counter Class counter Evaluation affects Hyper-v Hypervisor Virtual processor% Guest Runtime recommended VM size / cost Hyper-v dynamic memory VM current pressure (%)

Guests can see physical memory (MB) recommended VM size / cost Hyper-v virtual storage device reads bytes per second disk size, storage cost, VM size calculation of Hyper-v virtual storage device bytes per second disk size, storage cost, Calculation of VM size calculation of bytes per second received by Hyper-V virtual network adapter calculation of VM size calculation of bytes / second VM size sent by Hyper-V virtual network adapter

The following is a complete list of Hyper-v VM metadata collected by the device and sent to Azure.

Data WMI Class WMI Class Properties computer details BIOS Msvm_BIOSElement Serial number BIOSSerialNumberVM Type (Generation 1 or Generation 2) Msvm_VirtualSystemSettingDataVirtualSystemSubTypeVM display name Msvm_VirtualSystemSettingDataElementNameVM version Msvm_ProcessorSettingDataVirtualQuantity memory (bytes) maximum memory available Msvm_MemorySettingDataVirtualQuantityVM dynamic memory Msvm_MemorySettingDataDynamicMemoryEnabled operating system name / version / FQDNMsvm_KvpExchangeComponentGuestIntrinsicExchangeItems Name DataVM power status Msvm_ComputerSystemEnabledState per disk details disk identifier Msvm_VirtualHardDiskSettingDataVirtualDiskId virtual hard Disk type Msvm_VirtualHardDiskSettingDataType virtual hard disk size Msvm_VirtualHardDiskSettingDataMaxInternalSize virtual hard disk parent Msvm_VirtualHardDiskSettingDataParentPath per NIC details IP address (composite Nic) Msvm_GuestNetworkAdapterConfigurationIPAddressesDHCP enabled (composite Nic) Msvm_GuestNetworkAdapterConfigurationDHCPEnabledNIC ID (composite Nic) Msvm_SyntheticEthernetPortSettingDataInstanceIDNIC MAC address (composite Nic) Msvm_SyntheticEthernetPortSettingDataAddressNIC ID (old Nic) MsvmEmulatedEthernetPortSetting data InstanceIDNIC MAC ID (old Nic) MsvmEmulatedEthernetPortSetting data Address3, Discovery and collection process

The device uses the following procedure to communicate with the vCenter server and the Hyper-v host / cluster.

Start discovering: when you start discovery on a Hyper-v device, it communicates with Hyper-v hosts on WinRM ports 5985 (HTTP) and 5986 (HTTPS). When discovery is initiated on a VMware device, it communicates with the vCenter server on TCP port 443 by default. If the vCenter server listens on other ports, it can be configured in the device web application. Collect metadata and performance data: the device uses a Common Information Model (CIM) session to collect Hyper-v VM data on Hyper-v on host ports 5985 and 5986. By default, the device communicates with port 443 to collect VMware VM data from vCenter Server. Send data: the device sends the collected data to the Azure Migrate server for evaluation and migrates through the SSL port 443 Azure Migrate server. Devices can connect to Azure through internet, or Expre***oute can be used for public / Microsoft peer-to-peer interconnections. For performance data, the device collects real-time utilization data. For VMware, performance data is collected every 20 seconds, and for each performance metric, every 30 seconds. The collected data is summarized to create a single data point after 10 minutes. The peak utilization rate value is selected from all 20amp 30-second data points and sent to Azure for evaluation calculation. Sort the ten-hour hour in ascending order based on the percentile value specified in the evaluation attribute (50qqqninqqqq99), and calculate the evaluation using the appropriate percentile value. For server migration, the device begins to collect VM data and copy it to Azure. Evaluation and migration: you can now use Azure Migrate Server evaluation to create an evaluation from the metadata collected by the device. "alternatively, you can use Azure Migrate Server migration to start migrating VMware Vm to schedule agentless VM replication."

4. Equipment upgrade

The device is upgraded when the Azure Migrate agent running on the device is updated.

This occurs automatically because automatic updates are enabled by default on the device. You can change this default setting to update the agent manually. To disable automatic updates, in Registry Editor > HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ AzureAppliance, and set the registry key automatic updates to 0 (DWORD). Set agent updates to manual

For manual updates, ensure that all agents on the device are updated at the same time using the Update button for each obsolete agent on the device. You can switch the update settings back to automatic updates at any time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.