Migrating RabbitMQ Metadata to a RocketMQ Instance

Prerequisites

• A RocketMQ instance has been purchased.
• RabbitMQ plug-ins have been enabled.
• A RabbitMQ 3.7.17/3.8.35 instance has been purchased.

Step 1: Obtain RabbitMQ Metadata

1. Enter http://IP address of your RabbitMQ:15672/ in the address box of the browser to access the open-source RabbitMQ console.
2. On the login page, enter the username and password, and click Login.

   The default username and password are the ones configured in RabbitMQ instance purchase.

3. On the Overview tab page, click Download broker definitions to export the metadata.
   Figure 1 Exporting metadata
   

Step 2: Migrate Metadata on the Console

1. Log in to the console.
2. Click in the upper left corner to select a region.
   NOTE:

   Select the region where your RocketMQ instance is located.

3. Click and choose Application > Distributed Message Service for RocketMQ to open the console of DMS for RocketMQ.
4. Click a RocketMQ instance to go to the details page.
5. In the navigation pane, choose Metadata Migration.
6. Click Create Migration Task.
7. Configure the migration task by referring to Table 1.

   Table 1 Migration task parameters

   Parameter	Description
   Task Type	Select From RabbitMQ to RocketMQ.
   Task Name	Unique name of the migration task. A task name must meet the following requirements: Contains 4 to 64 characters. Contains only letters, digits, hyphens (-), and underscores (_), and must start with a letter.
   Overwrite	If this option is enabled, configurations in the metadata file with the same name as the uploaded file will be modified. Assume that Topic01 on the source instance has three read queues, and Topic01 on the DMS instance has two read queues. If Overwrite is enabled, Topic01 on the DMS instance will have three read queues after migration. If this option is disabled, migration of the metadata file with the same name as the uploaded file will fail. Assume that the source instance has Topic01 and Topic02, and the DMS instance has Topic01 and Topic03. If Overwrite is disabled, migration of the source Topic01 will fail.
   Metadata	Upload the RabbitMQ metadata.

8. Click OK.

   After the migration is complete, view Task Status in the migration task list.

   • If Task Status is Complete, all metadata has been successfully migrated.
   • If Task Status is Failed, some or all metadata fails to be migrated.

     Click the migration task name to go to the migration task details page. In the Migration Result area, view the name of the topic or consumer group that fails to be migrated, the failure cause, and the solution.