This topic provides guidelines on cross-region migrations. You can obtain an overview of your affected instances and solutions and precautions for migrations.
Background information
To optimize the global infrastructure of Alibaba Cloud and deliver more efficient services to customers, the physical infrastructures in some regions and zones need to be upgraded and rebuilt. Before the upgrades, you will be notified in advance to perform cross-region migrations if your resources are affected. This guide is provided to help you evaluate your affected instances and perform migrations.
Impact scope
You can use the resource collection feature of Cloud Migration Hub (CMH) to obtain an overview of your cloud resources deployed in the affected regions and check the topology of cloud services. For more information, see Survey Alibaba Cloud resources in online mode.
This feature is supported for primary instances of some cloud services. For more information, see the "Alibaba Cloud resources" section of the Supported source types and migration tools topic.
If you use other services or have questions about your affected cloud resources, submit a ticket for technical support.
You can use this feature in the CMH console.
Migration solutions
You can use different migration solutions in multiple scenarios based on your business requirements. This way, you can migrate your business from affected regions in an efficient manner.
CMH
If you use Virtual Private Cloud (VPC), Server Load Balancer (SLB), Elastic Compute Service (ECS), ApsaraDB RDS, and Object Storage Service (OSS), you can create migration plans in CMH to migrate all the resources in a region to another region. You can create region-based migration plans and specify cloud services for the migration plans to implement one-stop migration and configuration. For more information, see Migrate resources across regions on Alibaba Cloud.
You can create migration plans in the CMH console.
You can also use the following solutions to migrate your cloud resources separately.
ECS
You can use the snapshot and image features to migrate instance data. For more information, see Use a custom image to replicate ECS instances across regions. To facilitate your migration, CloudOps Orchestration Service (OOS) provides the ACS-ECS-CreateAndCopyImage template that can be used to automate cross-region image replications.
You can also use Server Migration Center (SMC) to migrate the data on servers to ECS instances. For more information, see Migrate servers to ECS instances.
Database (such as ApsaraDB RDS and ApsaraDB for HBase)
You can use Data Transmission Service (DTS) to migrate data between ApsaraDB RDS instances. For more information, see Synchronization topologies.
If your RDS instances run PostgreSQL, you can use the built-in cross-region migration feature. For more information, see Migrate data between ApsaraDB RDS for PostgreSQL instances that reside in different regions.
For ApsaraDB RDS for HBase or Lindorm, you can use Lindorm Tunnel Service to migrate your data. For more information, see Migrate and synchronize data from HBase clusters to Lindorm
Storage (such as OSS, NAS, Simple Log Service, EBS, Tablestore, and HBR)
OSS: You can use the cross-region replication (CRR) feature to migrate data between OSS buckets in different regions. You can also use Data Online Migration to implement more flexible migrations based on objects. For more information, see Background information and Migrate data.
File Storage NAS (NAS): You can use the Data Online Migration feature to migrate data between NAS file systems. For more information, see Preparations.
Simple Log Service: You can use the data transformation feature. The system reads data from a source Logstore and transforms the data to a destination Logstore. For more information, see Overview of data transformation.
Tablestore: You can use Tunnel Service to migrate data across tables in different regions. For more information, see Synchronize data from one table to another table in Tablestore.
Elastic Block Storage (EBS): If the cloud disks that you use have been attached to ECS instances, the data is migrated when you migrate ECS instances. If your cloud disks have not been attached to any ECS instances, you can migrate the data by creating a snapshot of a disk, copying the snapshot, and then creating a new disk from the snapshot.
Networking (such as EIP, CLB, ALB, CEN, NAT Gateway, VPN Gateway, VPN, HaVip, PVL, GA, and VPC)
You need to purchase and configure new network resources in the destination region.
For more information, see the following topics:
Elastic IP Address (EIP): Quick start
Classic Load Balancer (CLB): Overview
Application Load Balancer (ALB): Use an ALB instance to balance loads for IPv4 services
Cloud Enterprise Network (CEN): Use Enterprise Edition transit routers to connect VPCs in different regions and accounts
NAT Gateway: Create and manage an Internet NAT gateway
Express Connect: Connect an on-premises data center to a VPC by using an Express Connect circuit
VPN Gateway: Create and manage a VPN gateway
High-Availability Virtual IP Address (HAVIP): Create and manage an HAVIP
Global Accelerator (GA): Add and manage acceleration areas
VPC: Create a VPC with an IPv4 CIDR block
Big data (such as Elasticsearch, DataWorks, and MaxCompute)
You can use the following solutions to migrate your big data components.
Elasticsearch: You can use OSS to migrate data from a self-managed Elasticsearch cluster to an Alibaba Cloud Elasticsearch cluster. You can also use Alibaba Cloud Logstash to migrate data from a self-managed Elasticsearch cluster to an Alibaba Cloud Elasticsearch cluster, which can be used to implement near real-time data synchronization.
DataWorks: You can use the Migration Assistant service to batch migrate objects such as tasks, resources, and data sources. For more information, see Overview.
MaxCompute: You can use the batch synchronization feature or internal replication tools to migrate data. For more information, see, Overview of the batch synchronization feature.
E-MapReduce: For more information, see E-MapReduce data migration solution and Use Kafka MM2 to synchronize data across clusters.
Usage notes
If the IP addresses of resources such as ECS instances are changed, make sure that the IP configurations such as those in SLB instances, ECS security groups, and ApsaraDB RDS whitelists are adjusted accordingly. Otherwise, your applications may not be able to access the instances.
If you want to keep the private IP addresses configured in applications unchanged, you can create a VPC and a vSwitch that use the same CIDR block, and then change the private IP address of the new ECS instance deployed in the VPC to that of the old instance. For more information, see Modify a private IP address.
If the IP addresses and MAC addresses of your cloud resources are changed, make sure that the configurations in your applications are adjusted accordingly. The configurations include the direct IP connection configurations and the authorized IP addresses and MAC addresses.
After the migration is complete, make sure that your business traffic is fully switched to the new instances.
Check whether your business runs as expected. If you have questions about migration solutions or other items, submit a ticket for technical support.