If you directly switch the instance that is used as the registry and configuration center for applications to an MSE instance, the applications cannot obtain information from both the source and destination instances. To resolve this issue, MSE provides MSE Sync, which is a GUI-based migration tool. You can use MSE Sync to synchronize information between the source instance and the destination instance. This way, the applications can obtain information from both the source and destination instances. MSE Sync can help you smoothly migrate self-managed ZooKeeper instances and Nacos instances to MSE instances.
MSE Sync does not support the migration of Nacos configurations. If you need 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 .
On the Migration to Cloud page, click Specification evaluation. In the Specification evaluation panel, configure the parameters and click Specification evaluation.
Parameter
Description
Source instance type
Select Nacos or ZooKeeper.
Evaluation method
NoteSelect Assess by Self-managed Instance or Evaluated by Application Scale based on your business requirements.
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 the recommended instance specifications based on the evaluation result.
Click the purchase 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 .
On the Migration to Cloud page, click Migration configuration. In the Migration configuration panel, 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 type of the self-managed instance. You can select Nacos, Eureka, or ZooKeeper.
Source Instance Node Address
Enter the IP addresses of the nodes in the self-managed instance. If multiple node IP addresses are available, separate the IP addresses with carriage returns.
If the source instance uses Server Load Balancer (SLB) for load balancing, enter the IP address and port number of the SLB instance.
Source Instance Name
Enter the name of the self-managed instance.
Namespaces
You must specify this parameter if you select Nacos for Source instance type.
Enter the namespaces in the source instance from which you want to migrate the configurations. By default, you must enter the names of all namespaces. Separate namespaces with commas (,).
Destination Instance
Select the destination MSE instance.
Description
Enter a description of the migration task.
In the Implement migration step, perform the operations as prompted.