Real-Time Migration

You can migrate all database objects across cloud platforms, from on-premises databases to the cloud, or across regions on the cloud in real time. The following table lists the supported databases, versions, and migration types. For more information about real-time migration, see Real-Time Migration.

Self-managed databases (such as MySQL and MongoDB) include on-premises databases and databases created on ECSs. RDS for MySQL refers to the MySQL databases created using Huawei Cloud RDS.

Some functions are in restricted use. To use them, submit a service ticket.
The destination database version must be the same as or later than the source database version.

MySQL Serving as the Source in Migration

**Table 1** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
MySQL	Self-managed MySQL Versions 5.5, 5.6, 5.7, and 8.0 MySQL on other clouds Versions 5.5, 5.6, 5.7, and 8.0	RDS for MySQL All versions	Full Full+Incremental
		DDM The same version as that of the associated RDS instance.	Full Full+Incremental
		TaurusDB Compatible with MySQL 8.0	Full Full+Incremental
	RDS for MySQL All versions	RDS for MySQL All versions	Full Full+Incremental
		Self-managed or other cloud MySQL Versions 5.5, 5.6, 5.7, and 8.0	Full Full+Incremental
		DDM The same version as that of the associated RDS instance.	Full Full+Incremental
		TaurusDB Compatible with MySQL 8.0	Full Full+Incremental

MongoDB Serving as the Source in Migration

**Table 2** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
MongoDB	Self-managed MongoDB Versions 3.2, 3.4, 3.6, 4.0, 4.2, 4.4, and 5.0 MongoDB on other clouds Versions 3.2, 3.4, 3.6, 4.0, 4.2, 4.4, and 5.0 DDS Versions 3.2, 3.4, 4.0, 4.2, 4.4, and 5.0 NOTE: The source does not support GeminiDB Mongo.	DDS Versions 3.4, 4.0, 4.2, 4.4, and 5.0	Full Full+Incremental migration supports the following scenarios: Replica set -> Replica set Replica set -> Cluster Cluster -> Cluster Cluster -> Replica set NOTE: If the source is a DDS cluster instance, the incremental migration can only be performed when the source and destination databases are in the same VPC. If the source database is a DDS 3.2 cluster instance, only full migration is supported. Incremental migration is not supported because a DDS 3.2 cluster instance does not have a shard IP address. To perform a full+incremental migration for a single node instance, the source database must be a Huawei Cloud single node instance.
MongoDB	Self-managed MongoDB Versions 3.2, 3.4, and 4.0 MongoDB on other clouds Versions 3.2, 3.4, and 4.0 DDS Versions 3.4 and 4.0 NOTE: The source does not support GeminiDB Mongo.	GeminiDB Mongo Versions 3.4 and 4.0	Full Full+Incremental migration supports the following scenarios: Replica set -> Replica set Replica set -> Cluster Cluster -> Cluster NOTE: If the source is a DDS cluster, only full migration is supported.

AWS DocumentDB Serving as the Source in Migration

**Table 3** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
AWS Document	Replica set 4.0, replica set 5.0, and cluster 5.0	DDS instances (versions 3.4, 4.0, 4.2, 4.4, and 5.0)	Full Full+Incremental migration supports the following scenarios: Replica set -> Replica set Replica set -> Cluster Cluster -> Cluster Cluster -> Replica set NOTE: If the source database is a replica set, full+incremental, full, and incremental migration tasks are supported. If the source database is a cluster, only full migration tasks are supported. Currently, only synchronization tasks with AWS DocumentDB serving as the source are supported.

DDS Serving as the Source in Migration

**Table 4** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
DDS	DDS Versions 3.2, 3.4, 4.0, 4.2, 4.4, and 5.0	Self-managed MongoDB Versions 3.2, 3.4, 3.6, 4.0, 4.2, 4.4, and 5.0 MongoDB on other clouds Versions 3.2, 3.4, 3.6, 4.0, 4.2, 4.4, and 5.0	Full Full+Incremental migration supports the following scenarios: Replica set -> Single node Replica set -> Replica set Replica set -> Cluster Single node -> Single node Single node -> Replica set Single node -> Cluster NOTE: If the source database is a replica set, full+incremental and full migration tasks are supported. If the source database is a cluster, only full migration tasks are supported.

MySQL Schema and Logic Table Serving as the Source in Migration

**Table 5** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
MySQL schema and logic table	DDM	DDM	Full Full+Incremental

Redis Serving as the Source in Migration

**Table 6** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
Single-Node or Primary/Standby Redis	Self-managed official open-source single-node or primary/standby Redis Versions 2.8.x, 3.0.x, 3.2.x, 4.0.x, and 5.0.x	GeminiDB Redis	Full Full+Incremental

Redis Cluster Serving as the Source in Migration

**Table 7** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
Redis Cluster	On-premises open-source Redis Cluster Versions 3.0.x, 4.0.x, and 5.0.x ECS-hosted open-source Redis Cluster Versions 3.0.x, 4.0.x, and 5.0.x	GeminiDB Redis	Full+Incremental

GeminiDB Redis Serving as the Source in Migration

**Table 8** Database information
Source DB Engine	Source DB Type and Version	Destination DB Type and Version	Migration Type
GeminiDB Redis	GeminiDB Redis	Self-managed open-source Codis Version 3.0 or later Self-managed open-source single-node Redis Versions 2.8.x, 3.0.x, 3.2.x, 4.0.x, and 5.0.x Self-managed open-source primary/standby Redis Versions 4.0.x and 5.0.x	Full+Incremental
GeminiDB Redis	GeminiDB Redis	Self-managed open-source Redis Cluster Version 4.0 or later	Full+Incremental