RocketMQ Metadata Migration Overview

Scenario

RocketMQ service migration involves the following scenarios:

• Migrating RocketMQ from other vendors to DMS for RocketMQ.
• Migrating self-built RocketMQ to DMS for RocketMQ.
• Migrating one RocketMQ instance to another RocketMQ instance in the cloud.

Preparation

1. Configure the network.

   A RocketMQ instance can be accessed within a VPC or over a public network. For public network access, the producer and consumer must have public access permissions, and the following security group rules must be configured.

   Table 1 Security group rules

   Direction	Protocol	Port	Source	Description
   Inbound	TCP	8200	0.0.0.0/0	The port is used for public access to metadata nodes.
   Inbound	TCP	10100–10199	0.0.0.0/0	The port is used for accessing service nodes.

2. Buy a DMS for RocketMQ instance.

   For details, see Buying a RocketMQ Instance.

3. A Linux host is available, JDK v1.8.111 or later has been installed on the host, and related environment variables have been configured.