When migrating your registry and configuration center to the cloud, directly switching the client to the new registry and configuration center may cause the client to lose awareness of information from either center. To address this issue, MSE provides a cloud migration capability. Through the MSE Sync white-screen migration tool, you can synchronize information between the source and target clusters, enabling the client to perceive information from both clusters simultaneously. In addition, MSE supports seamless migration of self-managed registry and configuration centers such as ZooKeeper and Nacos to MSE, providing you with more flexibility and choice.
MSE Sync does not support the migration of Nacos configurations. To migrate Nacos configurations, use the configuration export and import feature of MSE Nacos instances.
Step 1: Evaluate specifications
Log on to the MSE console, and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Migration to Cloud.
On the Migration To Cloud page, click Specification Evaluation, configure the parameters and click Specification Evaluation.
Parameter
Description
Source Instance Type
MSE supports the migration of multiple engine types to the cloud, including Nacos, and ZooKeeper.
Evaluation Method
NoteYou can select Assess By Self-managed Instance or Evaluated By Application Scale as needed.
If you select Assess By Self-managed Instance, specify the number of vCPUs and memory size of the self-managed instance in the Self-managed Instance Node Specifications section, and enter the number of instance nodes in the Number Of Self-built Instance Nodes section.
If you select Evaluated By Application Scale, enter the number of pods in the Container Service for Kubernetes (ACK) cluster or number of processes on the Elastic Compute Service (ECS) instance in the Number Of Application Instance Nodes section.
In the upper part of the Specification Evaluation panel, the system displays a link for you to purchase MSE instances and provides recommended instance specifications based on the evaluation result.
Click the Purchase MSE Instance link. On the buy page, configure information such as the virtual private cloud (VPC) and network information. After you confirm the information, click Buy Now.
Step 2: Start the migration
Log on to the MSE console, and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Migration to Cloud.
On the Migration To Cloud page, click Migration Configuration and configure parameters as prompted.
In the Deployment Tools step, follow the instructions to deploy the migration tool. After you deploy the migration tool, click Next.
In the Create Configuration step, configure the required parameters and click Next.
Parameter
Description
Source Instance Type
Select the engine type. MSE supports the migration of Nacos, Eureka, ZooKeeper, and Consul.
Synchronization Type
Supports full synchronization, configuration synchronization, and service synchronization.
Source Instance Node Address
Enter the node address of the engine. The format is node IP and port (e.g., 192.168.100.101:2181), with one address per line. If there are multiple node IP addresses, use a line break to separate them.
If the source cluster uses SLB for load balancing, enter the IP address and port number of the SLB instance.
Source Instance Name
(Optional) Enter the name of the source instance.
Namespaces
When the source instance type is set to Nacos, this parameter must be configured.
Enter the namespaces to be migrated, separated by commas (,). If left blank, all namespaces will be migrated by default.
Destination Instance
Select the destination instance to which you want to migrate.
Description
(Optional) Enter a description of the migration task.
In the Implement Migration step, perform the operations as prompted.