Merge pull request #287810 from v-sreedevank/03Oct-MigrationLimits

Parallel migration

Author: prmerger-automator[bot]

articles/migrate/how-to-scale-out-for-migration.md

@@ -6,7 +6,7 @@ ms.author: ajaypar
 ms.manager: roopesh.nair
 ms.service: azure-migrate
 ms.topic: how-to
-ms.date: 06/20/2024
+ms.date: 10/03/2024
 ms.custom: engagement-fy24
 ---
 
@@ -17,14 +17,18 @@ This article helps you understand how to use a scale-out appliance to migrate a
 
 Using the agentless migration method for VMware virtual machines you can:
 
-- Replicate up to 300 VMs from a single vCenter server concurrently using one Azure Migrate appliance.
-- Replicate up to 500 VMs from a single vCenter server concurrently by deploying a second scale-out appliance for migration.
+- Schedule replication for up to 300 VMs from a single vCenter server concurrently using one Azure Migrate appliance.
+- Schedule replication for up to 500 VMs from a single vCenter server concurrently by deploying a second scale-out appliance for migration.
 
-In this article, you will learn how to:
+In this article, you learn how to:
 
 - Add a scale-out appliance for agentless migration of VMware virtual machines
 - Migrate up to 500 VMs concurrently using the scale-out appliance.
 
+> [!NOTE]
+> While you can schedule replication for up to 300 VMs on a single appliance and up to 500 VMs using a scale-out appliance, the replication itself is limited by each appliance's capacity to replicate only 56 disks at a time. This means that although the VMs are scheduled concurrently, they will be replicated sequentially based on the appliance's available capacity. All scheduled VMs will eventually be replicated by the same appliance, but not all will start replication immediately.
+
+
 ##  Prerequisites
 
 Before you get started, you need to perform the following steps:
@@ -41,7 +45,7 @@ To learn how to perform the above, review the tutorial on [migrating VMware virt
 
 To add a scale-out appliance, follow the steps mentioned below:
 
-1. Click on **Discover** > **Are your machines virtualized?** 
+1. Select **Discover** > **Are your machines virtualized?** 
 1. Select **Yes, with VMware vSphere Hypervisor.**
 1. Select agentless replication in the next step.
 1. Select **Scale-out an existing primary appliance** in the select the type of appliance menu.
@@ -52,12 +56,12 @@ To add a scale-out appliance, follow the steps mentioned below:
 ### 1. Generate the Azure Migrate project key
 
 1. In **Generate Azure Migrate project key**, provide a suffix name for the scale-out appliance. The suffix can contain only alphanumeric characters and has a length limit of 14 characters.
-2. Click **Generate key** to start the creation of the required Azure resources. Do not close the Discover page during the creation of resources.
-3. Copy the generated key. You will need the key later to complete the registration of the scale-out appliance.
+2. Select **Generate key** to start the creation of the required Azure resources. Don't close the Discover page during the creation of resources.
+3. Copy the generated key. You'll need the key later to complete the registration of the scale-out appliance.
 
 ### 2. Download the installer for the scale-out appliance
 
-In **Download Azure Migrate appliance**, click  **Download**. You need to download the PowerShell installer script to deploy the scale-out appliance on an existing server running Windows Server 2019 or Windows Server 2022 and with the required hardware configuration (32-GB RAM, 8 vCPUs, around 80 GB of disk storage and internet access, either directly or through a proxy).
+In **Download Azure Migrate appliance**, select  **Download**. You need to download the PowerShell installer script to deploy the scale-out appliance on an existing server running Windows Server 2019 or Windows Server 2022 and with the required hardware configuration (32-GB RAM, 8 vCPUs, around 80 GB of disk storage and internet access, either directly or through a proxy).
 
 :::image type="content" source="./media/how-to-scale-out-for-migration/download-scale-out.png" alt-text="Download script for scale-out appliance":::
 
@@ -83,7 +87,7 @@ In **Download Azure Migrate appliance**, click  **Download**. You need to downlo
 
       `PS C:\Users\administrator\Desktop\AzureMigrateInstaller> .\AzureMigrateInstaller.ps1 `
 
-5. Select from the scenario, cloud, configuration and connectivity options to deploy the desired appliance. For instance, the selection shown below sets up a **scale-out appliance** to initiate concurrent replications on servers running in your VMware environment to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
+5. Select from the scenario, cloud, configuration, and connectivity options to deploy the desired appliance. For instance, the selection shown below sets up a **scale-out appliance** to initiate concurrent replications on servers running in your VMware environment to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
 
     :::image type="content" source="./media/how-to-scale-out-for-migration/script-vmware-scaleout-inline.png" alt-text="Screenshot that shows how to set up scale-out appliance." lightbox="./media/how-to-scale-out-for-migration/script-vmware-scaleout-expanded.png":::
 
@@ -130,26 +134,26 @@ In the configuration manager, select **Set up prerequisites**, and then complete
     > This is a new user experience in Azure Migrate appliance which is available only if you have set up an appliance using the latest OVA/Installer script downloaded from the portal. The appliances which have already been registered will continue seeing the older version of the user experience and will continue to work without any issues.
 
     1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key, and then copy the key that's shown.
-	2. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
+	2. The appliance verifies the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
     3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
 
-        :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and log in.":::
+        :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and sign in.":::
     4. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
 	    > [!NOTE]
         > If you close the login tab accidentally without logging in, refresh the browser tab of the appliance configuration manager to display the device code and Copy code & Login button.
-	5. After you successfully log in, return to the browser tab that displays the appliance configuration manager. If the Azure user account that you used to log in has the required permissions for the Azure resources that were created during key generation, appliance registration starts.
+	5. After you successfully sign in, return to the browser tab that displays the appliance configuration manager. If the Azure user account that you used to sign in has the required permissions for the Azure resources that were created during key generation, appliance registration starts.
 
         After the appliance is successfully registered, to see the registration details, select **View details**.
 
 #### Import appliance configuration from primary appliance
 
-To complete the registration of the scale-out appliance, click **import** to get the necessary configuration files from the primary appliance.
+To complete the registration of the scale-out appliance, select **import** to get the necessary configuration files from the primary appliance.
 
 1. Clicking **import** opens a pop-up window with instructions on how to import the necessary configuration files from the primary appliance.
 
     :::image type="content" source="./media/how-to-scale-out-for-migration/import-modal-scale-out.png" alt-text="Screenshot of the Import Configuration files modal.":::
 
-1. Login (remote desktop) to the primary appliance and execute the following PowerShell commands:
+1. Sign in (remote desktop) to the primary appliance and execute the following PowerShell commands:
 
     `PS cd 'C:\Program Files\Microsoft Azure Appliance Configuration Manager\Scripts\PowerShell' `
 
@@ -160,16 +164,16 @@ To complete the registration of the scale-out appliance, click **import** to get
 
 1. Copy the zip file created by running the above commands to the scale-out appliance. The zip file contains configuration files needed to register the scale-out appliance.
 
-1. In the pop-up window opened in the previous step, select the location of the copied configuration zip file and click **Save**.
+1. In the pop-up window opened in the previous step, select the location of the copied configuration zip file and select **Save**.
 
-    Once the files have been successfully imported, the registration of the scale-out appliance will complete and it will show you the timestamp of the last successful import. You can also see the registration details by clicking **View details**.
+    Once the files are successfully imported, the registration of the scale-out appliance completes and it shows you the timestamp of the last successful import. You can also see the registration details by clicking **View details**.
 1. **Install the VDDK**: The appliance checks that VMware vSphere Virtual Disk Development Kit (VDDK) is installed. If the VDDK isn't installed, download VDDK 6.7, 7, or 8(depending on the compatibility of VDDK and ESXi versions) from VMware. Extract the downloaded zip file contents to the specified location on the appliance, as indicated in the *Installation instructions*.
 
     The Migration and modernization tool uses the VDDK to replicate servers during migration to Azure.
 
 You can *rerun prerequisites* at any time during appliance configuration to check whether the appliance meets all the prerequisites.
 
-At this point, you should revalidate that the scale-out appliance is able to connect to your vCenter server. Click **revalidate** to validate vCenter Server connectivity from scale-out appliance.
+At this point, you should revalidate that the scale-out appliance is able to connect to your vCenter server. Select **revalidate** to validate vCenter Server connectivity from scale-out appliance.
 :::image type="content" source="./media/how-to-scale-out-for-migration/view-sources.png" alt-text="Screenshot shows view credentials and discovery sources to be validated.":::
 
 > [!IMPORTANT]
@@ -183,7 +187,7 @@ At this point, you should revalidate that the scale-out appliance is able to con
 
 With the scale-out appliance in place, you can now replicate 500 VMs concurrently. You can also migrate VMs in batches of 200 through the Azure portal.
 
-The Migration and modernization tool will take care of distributing the virtual machines between the primary and scale-out appliance for replication. Once the replication is done, you can migrate the virtual machines.
+The Migration and modernization tool takes care of distributing the virtual machines between the primary and scale-out appliance for replication. Once the replication is done, you can migrate the virtual machines.
 
 > [!TIP]
 > We recommend migrating virtual machines in batches of 200 for optimal performance if you want to migrate a large number of virtual machines.