If a service on a VMware virtual machine is interrupted, you can restore the virtual machine locally to ensure service availability. However, if your on-premises infrastructure fails due to events such as an ESXi host breakdown or a data center outage, you can use the Cloud Backup console to restore the backed-up virtual machine as an Alibaba Cloud ECS instance. This ensures business continuity. During the restore process, the system automatically creates a temporary intermediate instance to recover the data. After the restore is complete, the intermediate instance is automatically released, and you can immediately use the destination ECS instance.
Prerequisites
You have backed up the VMware virtual machine.
The VMware virtual machine meets the requirements for operating systems and VMware platforms that are supported by Alibaba Cloud ECS.
The destination region has the required network resources to configure the network for the destination ECS instance:
A virtual private cloud (VPC) and a vSwitch. The zone of the vSwitch determines the ECS instance types that are 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 that are 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 job fails, its status changes to Failed and the related image information is displayed. In this case, the system has created an ECS image but failed to create an ECS instance. You can use the 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. The image is named in the format of
restore-{VM name}-hbr-{restore job ID}.In the Actions column of the image, click Create Instance.
On the Custom Launch tab, the system automatically specifies the region and image. Configure the other configuration items as prompted and click Confirm Order.
A restore job may fail because of environment incompatibility between the source virtual machine and the destination ECS instance. For example, the operating system version is not supported, or the configurations of the source virtual machine do not meet ECS requirements.
Step 3: Post-restore validation and resource cleanup
The destination ECS instance that is created from the restore job is billed on a pay-as-you-go basis. We recommend that you validate your workload and release unnecessary resources in a timely manner to avoid incurring unwanted fees.
Validate the workload: Use a remote connection tool, such as Remote Desktop Protocol (RDP) for Windows or Secure Shell (SSH) for Linux, to log on to the destination ECS instance and verify the integrity of the system and business data.
Release resources: If the restore job is performed only for validation or testing, release the instance in the ECS console to avoid unnecessary charges.
Delete images (for failed restore jobs only): If you manually created an ECS instance in Step 2, you can delete the unnecessary images on the Custom Images tab of the ECS console. When you delete an image, we recommend that you also delete its associated snapshots.