Q: When you deploy Microsoft Migration Accelerator, which components are installed on-premises and which are installed into your Microsoft Azure subscription?
A: Microsoft Migration Accelerator leverages the technology that was acquired as part of Microsoft's InMage Scout acquisition. This is the same technology used for Azure Site Recovery protection for non-Hyper-V sources to Microsoft Azure, as well as VMware to VMware protection. A migration is really just a replication to a target—a failover that never fails back. Therefore, it makes sense that Microsoft is now leveraging the technology as a migration solution.
The following figure shows all the components required for Microsoft Migration Accelerator and where they reside.
- 1: These are the workloads being migrated; for example, virtual machines running on VMware. Inside the OS instances being migrated is the Mobility Service, which captures the changes to the file system—which are sent to the Process Server.
- 2: The Process Server receives the changes to the file system, caches them, and then forwards them to the Master Target over a secure channel.
- 3: The Configuration Server is the centralized management component that runs in a customer's Azure subscription. It communicates with all other roles to control configuration via HTTPS (the other roles poll the Configuration Server).
- 4: The Master Target runs in the customer's Azure subscription as a virtual machine, receives the changes to OS instances being migrated, and writes those changes to virtual hard disks that are attached to the Master Target. At migration time, the disks are attached to actual virtual machines that will run the workload in Azure.
- 5: The Azure Multi-tenant Portal is used for configuration and runs outside of the Azure subscription but communicates to the Configuration Server instance.