tencent cloud

All product documents
Cloud Virtual Machine
DocumentationCloud Virtual Machine
Cross-AZ Migration
Last updated: 2024-09-11 21:33:02
Cross-AZ Migration
Last updated: 2024-09-11 21:33:02

Operation scenarios

In some availability zone data centers, outdated equipment may affect the stable operation of the business, or due to changes in its own business scenarios, the cross-regional migration capability is needed to migrate CVM instances to other availability zones.

Restrictions before migration

Migration is not supported for instances in the pending recycling status. If migration is needed, it is recommended to first restore the instance in the recycle bin.
Migration is not supported for instances with no charge for shutdown. If migration is needed, it is recommended to adjust the instance to be charged after shutdown.
Migration is not supported for instances with local disks or General Cloud Block Storage (CBS). If migration is needed, adjust the local disk or General CBS to High Performance or SSD CBS before migration (Operation path: Instance list > More actions > Resource adjustment > Adjust Disk Medium).
Migration is not supported for instances with system disks or data disks that are encrypted. If migration is needed, it is recommended to first uninstall the disks.
Migration is not supported for instances with swap disks. If migration is needed, unmount the swap disks first.
All CBS included in the selected instance must have snapshots created before migration can occur (Operation Path: Go to the Cloud Block Storage page > Select CBS > Create Snapshot, proceed to CBS page).
Instances with basic network configurations are not supported for migration. To migrate, please switch to VPC first (Operation Path: Instance list > More actions > Resource adjustment > Switch to VPC).
Instance migration must be performed in shutdown status.
Batch selection of instances across multiple availability zones and multi-instance families (e.g., Standard, Memory Optimized, Compute-Optimized) is not supported for migration. It is recommended to select instances in the same availability zone and the same instance family at a time for migration.
Bidding Instances, CDH-charged Dedicated instances, and Special Models are not supported for migration.
After instance migration, intranet communication latency between multiple instances in the same subnet across availability zones may increase. To ensure the normal operation of your business, it is recommended that you migrate all instances in the same subnet at one time.

Operation step

1. In the CVM Console > Instance List page, select instances in the same availability zone and the same instance family, click More actions > Instance settings > Instance Cross-Region Migration to enter the instance cross-region migration window.

2. According to the prompts, make preparations before migration. For example, create snapshots in advance: Cross-region migration involves migrating data in the hard disk by rolling back snapshots. Therefore, you need to create a full snapshot in advance. To ensure that the migrated instance is up-to-date, it is recommended to create snapshots within 24 hours.
Within the instance migration pop-up, click on Create Snapshot for the relevant instance to navigate to the Cloud Disk page and create a snapshot. Once the snapshot creation is complete, refresh the pop-up information.
3. After the snapshot is created, click Next .

4. Select the target availability zone for migration.

5. Select configuration adjustments: by default, the same instance specifications are selected, but you can choose other instance specifications.

6. Migrating to another availability zone may involve price changes. For example, the same specifications might have different prices in different availability zones, or the user might incur different costs due to upgrading/downgrading the configuration during migration. After confirmation, click Next .

7. When the instance is in a running state, it needs to be shut down before migration. You can select force shutdown, but be aware that forced shutdown may result in data loss or file system corruption. It is recommended to shut down proactively before initiating the migration.



8. Initiate the migration, you can view the migration progress. After the migration is complete, close the window.

FAQs

During cross-regional migration, will the availability zone attribute of the subnet change?

It will not change with the migration. The user must decide when to change the subnet's availability zone attribute.

For the EIP bound to a CVM under the classic network, if the CVM is migrated to another availability zone, does the EIP need to be unbound and re-bound, or can it migrate with the CVM?

It will not migrate with the CVM. The user needs to unbind and rebind it.

Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon