Real-Time Migration

In real-time migration, you only need to configure the source database, destination database, and migration objects. DRS will help you compare and analyze data so you can determine when to migrate with minimal service disruption.

Only whitelisted users can use this function. To use this function, submit a service ticket. In the upper right corner of the management console, choose Service Tickets > Create Service Ticket to submit a service ticket.

Supported Database Types

DRS supports migration between different DB engines. The following table lists the supported data sources. Self-built databases include on-premises databases and ECS databases.

**Table 1** Database types
Migration Direction	Data Flow	Source DB	Destination DB	Destination DB Type
To the cloud	MySQL->MySQL	On-premises databases ECS databases Databases on other clouds RDS for MySQL DB instances	RDS for MySQL DB instances	Single Primary/Standby
To the cloud	MySQL->DDM	On-premises databases ECS databases Databases on other clouds RDS for MySQL DB instances	DDM instances	-
To the cloud	MySQL->TaurusDB	On-premises databases ECS databases Databases on other clouds RDS for MySQL DB instances TaurusDB instances	TaurusDB	Primary/Standby
To the cloud	MongoDB->DDS	On-premises databases ECS databases Databases on other clouds DDS DB instances	DDS DB instances	Cluster Replica set Single node
To the cloud	MongoDB->GeminiDB Mongo	On-premises databases ECS databases Databases on other clouds	GeminiDB Mongo instances	Cluster Replica set
To the cloud	Redis->GeminiDB Redis	On-premises official open-source single-node or master/standby Redis ECS-hosted official open-source single-node or master/standby Redis	GeminiDB Redis instances	-
To the cloud	MySQL schema and logic table -> DDM	DDM instances	DDM instances	-
From the cloud	MySQL->MySQL	RDS for MySQL DB instances	On-premises databases ECS databases Databases on other clouds	Single Primary/Standby
From the cloud	DDS->MongoDB	DDS DB instances	On-premises databases ECS databases Databases on other clouds	Cluster Replica set Single node

**Table 2** Database versions
Migration Direction	Data Flow	Source DB Version	Destination DB Version
To the cloud	MySQL->MySQL	MySQL 5.5.x MySQL 5.6.x MySQL 5.7.x MySQL 8.0.x	MySQL 5.6.x MySQL 5.7.x MySQL 8.0.x
To the cloud	MySQL->TaurusDB	MySQL 5.6.x MySQL 5.7.x MySQL 8.0.x	TaurusDB-MySQL 8.0
To the cloud	MySQL->DDM	MySQL 5.6.x MySQL 5.7.x	The version of the RDS DB instance associated with the destination DB is the same as the source DB version.
To the cloud	MongoDB->DDS	MongoDB 3.2.x MongoDB 3.4.x MongoDB 3.6.x MongoDB 4.0.x MongoDB 4.2.x MongoDB 4.4.x	DDS 3.2.x DDS 3.4.x DDS 4.0.x DDS 4.2.x DDS 4.4.x
To the cloud	MongoDB->GeminiDB Mongo	MongoDB 3.4.x MongoDB 4.0.x	GeminiDB Mongo 3.4.x GeminiDB Mongo 4.0.x
To the cloud	MySQL schema and logic table -> DDM	-	-
To the cloud	Redis->GeminiDB Redis	Redis 2.8.x Redis 3.0.x Redis 3.2.x Redis 4.0.x Redis 5.0.x	GeminiDB Redis 5.0 or earlier
From the cloud	MySQL->MySQL	MySQL 5.6.x MySQL 5.7.x MySQL 8.0.x	MySQL 5.6.x MySQL 5.7.x MySQL 8.0.x
From the cloud	DDS->MongoDB	DDS 3.2.x DDS 3.4.x DDS 4.0.x DDS 4.2.x DDS 4.4.x	MongoDB 3.2.x MongoDB 3.4.x MongoDB 3.6.x MongoDB 4.0.x MongoDB 4.2.x MongoDB 4.4.x

Supported Migration Types

DRS supports two migration types: full migration and full+incremental migration.

This full migration type is suitable for scenarios where service interruption is acceptable. All objects and data in non-system databases are migrated to the destination database at one time. The objects that can be migrated include tables, views, stored procedures, and triggers.

The full+incremental migration type allows you to migrate data without interrupting services. After a full migration initializes the destination database, an incremental migration parses logs to ensure data consistency between the source and destination databases.

**Table 3** Migration types
Migration Direction	Data Flow	Full Migration	Full+Incremental Migration
To the cloud	MySQL->MySQL	Supported	Supported
To the cloud	MySQL->TaurusDB	Supported	Supported
To the cloud	MySQL->DDM	Supported	Supported
To the cloud	MongoDB->DDS	Replica set -> Single node Replica set -> Replica set Replica set -> Cluster Single node -> Single node Single node -> Replica set Single node -> Cluster Cluster -> Cluster	Replica set -> Single node Replica set -> Replica set Replica set -> Cluster Single node -> Single node Single node -> Replica set Single node -> Cluster Cluster -> Cluster Cluster -> Replica set NOTE: If you need to perform an incremental migration for a single-node instance, the source database must be the DDS single-node instance. If the source database is a DDS cluster instance, an incremental migration is supported only in the VPC scenario. The source database cannot be a GeminiDB Mongo instance.
To the cloud	MongoDB->GeminiDB Mongo	Replica set -> Replica set Replica set -> Cluster Cluster -> Cluster Single node -> Replica set Single node -> Cluster	Replica set -> Replica set Replica set -> Cluster Cluster -> Cluster NOTE: If the source database is a DDS DB instance, full and incremental migration between clusters is not supported. To perform a full plus incremental migration for a single node instance, the source database must be on the Huawei Cloud. The source database cannot be a GeminiDB Mongo instance.
To the cloud	MySQL schema and logic table -> DDM	Supported	Supported
To the cloud	Redis->GeminiDB Redis	Supported	Supported
From the cloud	MySQL->MySQL	Supported	Supported
From the cloud	DDS->MongoDB	Supported	Supported NOTE: If the source database is on a cluster instance, incremental migration is not supported.

Supported Network Types

DRS supports data migration through a Virtual Private Cloud (VPC), Virtual Private Network (VPN), Direct Connect, or public network. Table 4 lists the application scenarios of each network type and required preparations, and Table 5 lists the supported network types of each migration scenario.

**Table 4** Network types
Network Type	Application Scenario	Preparations
VPC	Migrations between cloud databases in the same region	The source and destination databases must be in the same region. The source and destination databases can be in either the same VPC or in different VPCs. If source and destination databases are in the same VPC, they can communicate with each other by default. Therefore, you do not need to configure a security group. If the source and destination databases are not in the same VPC, the CIDR blocks of the source and destination databases cannot be duplicated or overlapped, and the source and destination databases are connected through a VPC peering connection. DRS does not support communication between the source database and destination database over a VPC across tenants. If necessary, you can create a VPC peering connection and select VPN for Network Type to enable communication between the source and destination databases. For details about how to create a VPC peering connection, see Virtual Private Cloud User Guide.
VPN	Migrations from on-premises databases to cloud databases or between cloud databases across regions	Establish a VPN connection between your local data center and the VPC that hosts the destination database. Before migration, ensure that the VPN network is accessible. For more information about VPN, see Getting Started with Virtual Private Network.
Direct Connect	Migrations from on-premises databases to cloud databases or between cloud databases across regions	Use a dedicated network connection to connect your data center to VPCs. For more information about Direct Connect, see Getting Started with Direct Connect.
Public network	Migrations from on-premises or other cloud databases to destination databases	To ensure network connectivity between the source and destination databases, perform the following operations: Enable public accessibility. Enable public accessibility for the source database based on your service requirements. Configure security group rules. Add the EIPs of the replication instance to the whitelist of the source database for inbound traffic. If destination databases and the replication instance are in the same VPC, they can communicate with each other by default. You do not need to configure a security group. NOTE: The IP address on the Configure Source and Destination Databases page is the EIP of the replication instance. If SSL is not enabled, migrating confidential data is not recommended.

**Table 5** Supported network types
Migration Direction	Data Flow	VPC	Public Network	VPN or Direct Connect
To the cloud	MySQL->MySQL	Supported	Supported	Supported
To the cloud	MySQL->TaurusDB	Supported	Supported	Supported
To the cloud	MySQL->DDM	Supported	Supported	Supported
To the cloud	MongoDB->DDS	Supported	Supported	Supported
To the cloud	MongoDB->GeminiDB Mongo	Supported	Supported	Supported
To the cloud	MySQL schema and logic table -> DDM	Supported	Supported	Supported
To the cloud	Redis->GeminiDB Redis	Supported	Supported	Supported
From the cloud	MySQL->MySQL	Supported	Supported	Supported
From the cloud	DDS->MongoDB	Supported	Supported	Supported

Migration Objects

DRS allows you to migrate objects at different levels. The following table lists the supported migration objects.

**Table 6** Supported migration objects
Migration Direction	Data Flow	Full Migration	Table-Level Migration	Database-Level Migration
To the cloud	MySQL->MySQL	Supported	Supported	Supported
To the cloud	MySQL->TaurusDB	Supported	Supported	Supported
To the cloud	MySQL->DDM	Not supported	Supported	Not supported
To the cloud	MongoDB->DDS	Supported	Supported	Supported
To the cloud	MongoDB->GeminiDB Mongo	Supported	Supported	Supported
To the cloud	MySQL schema and logic table -> DDM	Not supported	Supported	Not supported
To the cloud	Redis->GeminiDB Redis	Not supported	Not supported	Supported
From the cloud	MySQL->MySQL	Supported	Supported	Supported
From the cloud	DDS->MongoDB	Supported	Supported	Supported

Advanced Features

DRS supports multiple features to ensure successful real-time migration.

**Table 7** Advanced features
Feature	Description
Flow control	Allows you to limit the overall migration speed to make the impact of migration on bandwidth and database I/O controllable. Flow control mode takes effect only during a full migration.
Account migration	Allows you to migrate accounts, permissions, and passwords.
Parameter comparison	Checks the consistency of common parameters and performance parameters between source and destination databases to ensure that the migrated service is running properly.