Migration Notice
Resource Migration (UCloud Global Resource Migration) provides the migration and integration services of cloud service resources. According to different scenario needs, the platform provides the following two migration methods:
- Cross-project resource migration
- Cross-cloud service account resource migration
Migration Rules
The types of resources that can be migrated include cloud hosts, network environments, storage, and cloud databases. We will default to migrate resources such as EIP and UDisk bound to your cloud host. If you only need to migrate the cloud host, please unbind other resources first. The specific product types and corresponding migration rules are as follows:
| Product Type | Requirement | Migration Rules |
|---|---|---|
| Cloud Host UHost | No expiration Disk encryption has not been enabled Data Ark has not been activated Hardware Isolation is not enabled Not bound to Load Balancer ULB Non postpaid resources Not big data D host type Not private area resources Not Container Cloud Host | Before and after migration, the resource ID, internal network IP, and MAC address of the cloud host do not change. |
| Cloud Disk UDisk (including system disk, data disk) | - | Before and after migration, the resource ID and mounting status of the disk do not change. |
| Local Disk (including system disk, data disk) | - | Before and after migration, the resource ID and mounting status of the disk do not change. |
| Elastic IP EIP | Not bound to shared bandwidth No bandwidth package in use | Before and after migration, the EIP address remains the same. |
| Private Network VPC | - | Before and after migration, the VPC segment remains the same; If the VPC to be migrated is interconnected with other VPCs, please reopen it after migration. |
| Subnet | - | Before and after migration, the subnet segment remains the same. |
| Firewall | - | Before and after migration, firewall access rules remain the same. |
| Gateway NAT | - | Before and after migration, NAT gateway forwarding rules remain the same. |
| Access Control List ACL | - | Before and after migration, the rules for data inflow and outflow remain the same. |
| Route Table URouteTable | - | Before and after migration, route table routing rules remain the same. |
| Cloud DatabaseUDB MySQL | Not expired The backup to US3 function was not enabled when migration was initiated Only supports NVMe and CLOUD_SSD models Does not support Proxy migration | Before and after migration, route table routing rules remain the same. |
Note: The final migration resources prevail
Preparations
The migration process will be accompanied by a brief business interruption, to ensure the smooth progress of your resource migration, please check your environment to ensure the completion of the following preparations:
- The status of the cloud service account of the resource migration party is normal, and real-name authentication has been completed;
- After the migration begins, we will automatically settle the cost of the resources already used for you and refund the unused portion of the amount.
- After the migration is complete, we will automatically renew the resources for one cycle on the migration side. Please check that the balance of the resource migration party is sufficient;
- Please check that the resources to be migrated have not expired;
- Please check that the quota of the resource migration party is sufficient (i.e. EIP quota is sufficient);