Edit

Migrate VMware VMs to Azure Local using Azure Catalyst

Applies to: Azure Local 2503 and later

This article describes how to migrate the VMware virtual machines (VMs) to Azure Local using Azure Catalyst. It also includes the steps to verify the migration.

Before you begin

Before you migrate your VMware VMs:

Migrate VMware VMs

  1. In the Azure portal, go to your project and select Server replication.

    Screenshot of the Server replication page for a project in the Azure portal.

  2. From the command bar, select Migrate to migrate multiple VMs that are ready.

    Screenshot of the Server replication page with Migrate highlighted on the command bar.

    Alternatively, select Ready to migrate for a single VM, or select ... next to the VM and then select Migrate.

    Screenshot of the Server replication page with Migrate selected from the context menu for a VM.

  3. On the Migrate page:

    1. Review the details of the VMs that you want to migrate.
    2. Select whether or not you would like to shut down VMs before migration. We recommend that you shut down VMs as that ensures no data is lost.
    3. Select Migrate to start the migration. A notification appears that the migration has started.

    Screenshot of Migrate page with context menu in Azure portal.

  4. Refresh the page periodically to view the migration status. You can also select the migration status at any time to view the progress details.

    The Planned failover blade indicates the various migration tasks in progress. Screenshot of Planned failover for a VM in Azure portal.

    The migration status changes from Migration in progress to Completed when the migration is complete.

Once the migration is complete, the VMs are running on your Azure Local instance. You can view the VMs in the Azure portal.

Verify and complete migration

Important

After verifying the status of the migrated VM, be sure to complete migration as detailed below. Don't manually delete the seed disks or other replication artifacts. Failing to complete migration or deleting these artifacts can cause unexpected behavior.

  1. In the Azure portal, go to your Azure Local resource, then select Virtual machines.

  2. In the list of VMs in the right-pane, verify that the VMware VMs that you migrated are present.

    Screenshot of Azure Local > Virtual machines in Azure portal.

  3. Select a VM to view its details. Verify that:

    1. The VM is running. The corresponding source VM on the source ESX server is turned off.
    2. The VM has the disk and network configuration as configured during replication.

    Screenshot of migrated VM details in Azure portal.

  4. Sign into the VM using Hyper-V VMConnect. Verify that:

    1. The VM behaves as expected.
    2. Your applications work as expected.
  5. In the Azure portal, go to your project and select Server replication. Select ... next to the VM, and then select Complete migration.

    Alternatively, select the VM name.

    Screenshot of Replications view with a VM selected in Azure portal.

    From the top command bar, select Complete migration. When prompted for confirmation, select Yes to continue.

    Screenshot of confirmation to complete migration in Azure portal.

    Repeat this action for all the migrated VMs.

    The Complete migration action starts the Delete protected item job, which you can track on the Jobs page of your project. This job removes the replication state and service-managed replication artifacts without affecting the migrated VM.

    Screenshot of the Jobs page with a Delete protected item job highlighted.

    A seed disk is a temporary disk that contains the replicated source data used to create the final migrated disk. As part of its cleanup, the standard Complete migration operation deletes seed disks and other replication artifacts, such as a seed ISO attached to the migrated VM. If you don't complete migration, these artifacts remain on the target system and continue to use storage.

    After the migrated resource is deleted, it's also removed from the Server replication view. The source VM is no longer protected, and you can enable replication again for the same source VM if needed.

Clean up

Once you have verified that migration is complete and no more machines need to be migrated, the last step is to clean up. Cleanup requires deletion of the following resources created during migration:

  • Source VMs and the associated VM disks from VMware vCenter.
  • Source VMware appliance and target Azure Local appliance VMs.

Enable guest management

After migrating a VM, you might want to enable guest management on that VM. For more information, see Enable guest management.

You can enable guest management only on Windows Server 2016 or later, and on Linux guests with Linux Integration Services. For more information, see Supported Guest OS.

Next steps