Welcome to the subsequent stage of your VMware to Azure migration journey. On this a part of the information, you’ll full server dependency mapping.
Overiew of Dependency Mapping
Servers have dependencies in manufacturing and real-world environments. For instance, an software server might rely upon a database server.
Moreover, a server might require some firewall ports to be opened to speak with different servers.
The Azure Migrate dependency evaluation identifies found on-premises servers and their inter-dependencies. After working your dependency evaluation and mapping, you possibly can plan your migration by:
- Determine servers that you have to migrate collectively
- Modify your Azure evaluation teams to enhance migration success
- Decide servers that have to be decommissioned as a result of they’re not in use.
Dependency evaluation helps you propose your migration and cut back shock service outages. Azure Migrate helps two forms of dependency evaluation: agentless and agent-based.
On this information, I’ll clarify the best way to carry out agentless dependency mapping.
Job 1: Carry out Agentless Dependency Mapping
Agentless dependency evaluation helps VMware, Hyper-V, and servers working on public clouds like AWS and GCP. The steps beneath clarify the best way to full agentless dependency evaluation on VMware found VMs:
- On the Servers, databases and internet apps > Azure Migrate: Discovery and evaluation web page, click on the Dependency evaluation drop-down and select Add servers.
- On the Dependency evaluation – Add servers web page, solely found servers which were validated as prepared for migration will likely be obtainable. Verify all of the servers on which you need to run dependency evaluation, then click on Add servers.
Job 2: View Server Dependencies
- As soon as the earlier activity is accomplished, increase Handle, then click on the Found servers menu. To show a server’s dependencies, click on View dependencies.
- The final motion will show the server’s dependincy mapping. The dependincy mapping for my area controller exhibits that 6 purchasers are linked to the server.
To view the purchasers, click on the arrow subsequent to the node.
Moreover, the mapping exhibits that there are 15 processes working on the DC and 6 ports that apps and different servers use to hook up with the server.
To view the detailed dependency mapping for the server, click on on it to increase it. The screenshot beneath exhibits that there’s 1 Inbound Connection and 6 Outbound Connections.
Nonetheless, there is no such thing as a different machine that depends upon this VM to operate.
The TCP/IP inbound and outbound join will aid you plan the Community Safety Grouy inbound and outbound guidelines for the Azure Digital community this VM will likely be migrated into.
Job 3: Refine Grouping Primarily based on Dependency Evaluation
Primarily based on the dependency mapping you carried out in Job 2, refine the group you created earlier.
So as to add or take away servers from a gaggle:
- Click on the quantity beneath Teams
- Then, click on on a gaggle’s identify and at last, click on Add machines or Take away machines.
After finishing dependency mapping for all of the VMware workloads you propose emigrate, it’s time to migrate the VMs to Azure. For the steps, proceed to half 4 of this information.
