Marketplace Architecture

As part of Dr Migrate’s solution, the Azure Migrate appliance is used to discover servers in a customer’s environment. All data collected by the Azure Migrate appliance is securely sent via HTTPS and encrypted at rest within the customer’s Azure tenant, ensuring it remains within customer network boundaries.

Dr Migrate is deployed directly into the customer’s Azure tenant via the Azure Marketplace. During the automated deployment, Dr Migrate synchronizes with Azure Migrate using the provided limited access SPN and begins data analysis. Near-real-time insights are accessible through the Dr Migrate web interface.

Key Points:

• The Azure Migrate appliance requires read-only access to target hypervisors, VMs, and servers.
• Data is encrypted at rest and in transit.
• Data is sent from the Azure Migrate appliance to the Azure Migrate Project over port 443.
• Dr Migrate ingests data from the Azure Migrate Project via REST API.

Key Architecture Components

Dr Migrate Manage Resource Group

As a part of the Azure Marketplace deployment, a Managed Resource Group is automatically setup, with the following services deployed.

VM Specifications

Data Flow

Data is synchronized between Azure Migrate Appliance > Azure Migrate Project > Dr Migrate.

Azure Marketplace Hosted Architecture FAQ

Does Dr Migrate require access to on-premises servers? Dr Migrate does not require access to any on-premises devices, Azure Migrate is used as the data collection source, securely dealing with both data in transit and at rest.

Does Dr Migrate and Azure Migrate need to be in the same Resource Group or Subscription? No, it is not essential, but they must be in the same Azure Tenant.

Does the Azure Migrate appliance analysis affect on-premises performance? The Azure Migrate appliance profiles on-premises servers continuously to measure performance data. This means that Azure Migrate will only collect telemetry when there is a low load on the target host. This profiling has almost no performance impact on profiled servers.

How much data is uploaded during continuous profiling? On average a server sends approximately 5 MB of data per day. This value is approximate; the actual value varies depending on the number of data points for the disks and NICs.

What network connectivity is required? The Azure Migrate appliance needs access to Azure URLs. Review the URL list here.

What data points should Azure Migrate be setup to collect? It is essential that Azure Migrate is configured to collect Software Inventory, Application Dependency, SQL Inventory and network data. This will allow Dr Migrate to provide comprehensive insights.

How many Azure Migrate Appliances do I need? As a rule of thumb:

• one per discovery method needed (i.e. one for VMware, Hyper-V, Physical).
• one per 500 to 1000 machines within the discovery method.

See Microsoft’s Online Common Questions regarding Azure Migrate for more information.

Whitelisting Remote Service Connections

In the event that an existing vnet is selected during installation as opposed to creating a new one then certain network comms will need to be whitelisted.

Use the comms table below as a guide.