All Products
Search
Document Center

Cloud Backup:Full-machine restore of VMware virtual machines to the cloud

Last Updated:Oct 09, 2026

When the services of a VMware virtual machine are interrupted, an on-premises restore usually resumes normal operations. If the underlying infrastructure fails (such as an ESXi host crash or a data center outage), use the Cloud Backup console to restore a backed-up virtual machine as an Alibaba Cloud ECS instance to ensure business continuity. During the restore, the system automatically creates a temporary intermediate instance to recover the data. After the restore is complete, the intermediate instance is released automatically, and you can immediately put the destination ECS instance back into service.

Prerequisites

Procedure

Important
  • You can restore only one VMware virtual machine at a time.

  • The intermediate ECS instance, destination ECS instance, disks, and images generated during the restore are billed based on the ECS billing rules. For more information about pricing, see ECS Billing.

Step 1: Restore to ECS

  1. Log on to the Cloud Backup console. In the left-side navigation pane, choose Backup > VMware Backup and Disaster Recovery, then at the top of the page, select the region where the resources are located.

  2. On the Backup Jobs tab, find the backup job that contains the target virtual machine, and click Restore to ECS in the Actions column.

  3. In the Create ECS Image dialog box, configure the virtual machine to restore and the intermediate instance.

    1. On the VMs to Restore step, select a virtual machine to restore, then click Next.

    2. On the Configure Intermediate Instance step, configure the intermediate instance using the parameters described in the following table.

      Parameter

      Description

      Hostname

      The hostname of the destination ECS instance.

      For Windows, the hostname must be 2 to 15 characters in length and can contain letters, digits, or hyphens (-). It cannot start or end with a hyphen, and cannot contain only digits.

      For Linux and other systems, the hostname must be 2 to 64 characters in length. You can use periods (.) to separate the hostname into multiple segments. Each segment can contain letters, digits, or hyphens (-), and cannot start or end with a period or hyphen.

      Instance Name

      The name of the intermediate ECS instance, which becomes the name of the destination ECS instance after the restore. The name can be up to 128 characters in length.

      VPC

      From the VPC list, select the VPC to use for the restore.

      vSwitch

      From the vSwitch list, select the vSwitch to use for the restore. The zone of the vSwitch determines the available ECS instance types.

      Instance Family

      The type of the intermediate ECS instance. Valid values: General Purpose, Compute Optimized, Memory Optimized, High Clock Speed, or Others. The available instance types change based on your selection.

      Instance Type

      The specifications of the intermediate ECS instance. For more information, see Overview of ECS instances.

      Note

      If the source instance uses UEFI boot, select a Generation 7 or later ECS instance. Otherwise, the instance may fail to start.

      Disk Type

      The disk type of the intermediate ECS instance. Valid values: Ultra Disk and SSD Cloud Disk.

      Note

      All disks of the virtual machine are set to the same disk type. Only disks larger than 40 GB support the AutoPL type.

      Security Group

      From the Security Group list, select the security group to use for the restore.

      IP Address Type

      The private IP address assignment method of the destination ECS instance. Select DHCP for automatic assignment, or select Manual, then specify an IP address.

      Operating System

      The system automatically detects and displays the operating system type of the source virtual machine. No manual configuration is required.

      Reboot After Restoration

      Specifies whether to automatically start the destination ECS instance after the restore. This option is enabled by default.

      Assign Public IP

      Specifies whether to assign a public IP address to the destination ECS instance. This option is disabled by default.

  4. Click OK.

    On the Restore Jobs tab, switch the job type to Cloud Restore Jobs, then view the restore progress. The restore process goes through the following stages:

    • Pending Execution: The system is preparing the restore environment.

    • Running: Data is transferred from the backup vault to the intermediate instance. The page displays the progress percentage and the restore speed.

    • Complete: The restore succeeded, and the intermediate instance is automatically released. The Destination column displays the name and instance ID of the destination ECS instance.

    Note

    The restore duration depends on factors such as the backup data size and network conditions.

Step 2: (Optional) Handle a failed restore

If the restore-to-ECS job fails, the job status shows Failed and the page displays the related image information. A failed restore means the system created an ECS image but did not create an ECS instance. You can use this image to manually create an ECS instance:

  1. Go to the Images page of the ECS console. On the Custom Images tab, find the image whose name contains the restore job ID (in the format restore-{VM name}-hbr-{restore job ID}).

  2. In the Actions column of the target image, click Create Instance.

  3. On the Custom Launch tab, the system automatically fills in the region and image information. Complete the other configurations as prompted, then click Create Order.

Note

A restore usually fails due to incompatibility between the source virtual machine and the destination ECS environment. For example, the operating system version is not supported, or the source virtual machine configuration does not meet ECS requirements.

Step 3: Post-restore validation and resource cleanup

The destination ECS instance generated by the restore is billed on a pay-as-you-go basis. Validate your workload and clean up unnecessary resources promptly.

  • Validate the workload: Connect to the destination ECS instance over RDP (Windows) or SSH (Linux), and verify the integrity of the system and business data.

  • Clean up resources: If the restore is only for validation or testing, release the instance in the ECS console promptly after the restore to avoid ongoing charges.

  • Clean up images (failed restore scenarios only): If you manually created an ECS instance in Step 2, you can delete the unnecessary images on the ECS console > Custom Images tab. When you delete an image, also delete its associated snapshots.