If a dedicated host has failure risks, it is still available. However, the dedicated host and the Elastic Compute Service (ECS) instances on it may fail at any time. You can migrate the dedicated host to another dedicated host to protect your services.
Prerequisites
All ECS instances on the dedicated host are stopped.
Service interruptions may occur when you stop instances. We recommend that you stop instances during off-peak hours.
Limits
You cannot migrate ECS instances that run on a local SSD dedicated host on your own. However, you can submit a ticket to request a migration. Data on the local SSDs of the dedicated host will be lost after the migration.
Impacts
After all the ECS instances on the dedicated host are migrated to another dedicated host, the host ID and the metadata of the ECS instances remain unchanged. This metadata includes the instance ID, private IP address, and public IP address of each ECS instance. However, the machine ID of the dedicated host is changed.
Procedure
Log on to the ECS console.
In the left-side navigation pane, choose Instances & Images >
> Dedicated Hosts. In the top navigation bar, select the region and resource group to which the resource belongs.
On the Host tab, find the dedicated host that you want to migrate. In the Status column, move the pointer over Physical Machine Risk. In the Note message, click Change Host.
Perform operations based on the dedicated host type.
If the dedicated host is not a local SSD host, click OK.
If the dedicated host is a local SSD host, click Submit Ticket.
WarningThe data on the local SSDs of the dedicated host will be lost after the migration.
Related operations
To migrate ECS instances, you can also refer to the following topics: