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
You have backed up the VMware virtual machine.
The VMware virtual machine meets the Alibaba Cloud ECS limits for operating systems and VMware platforms.
The destination region has the following network resources, which are required to set up the network of the destination ECS instance:
A virtual private cloud (VPC) and a vSwitch. The zone of the vSwitch determines the ECS instance types available for the restore.
A security group in the VPC.
Procedure
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 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:
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}).In the Actions column of the target image, click Create Instance.
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.
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.