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.
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.
Migration Direction | Data Flow | Source DB | Destination DB | Destination DB Type |
---|---|---|---|---|
To the cloud | MySQL->MySQL |
| RDS MySQL DB instances |
|
To the cloud | MySQL -> GaussDB(for MySQL) primary/standby |
| GaussDB(for MySQL) primary/standby |
|
To the cloud | MongoDB->DDS |
| DDS DB instances |
|
From the cloud | MySQL->MySQL | RDS MySQL DB instances |
|
|
From the cloud | DDS->MongoDB | DDS DB instances |
|
|
Self-built -> Self-built | MySQL->MySQL |
|
|
|
Migration Direction | Data Flow | Source DB Version | Destination DB Version |
---|---|---|---|
To the cloud | MySQL->MySQL |
|
|
To the cloud | MongoDB->DDS |
|
|
To the cloud | MySQL -> GaussDB(for MySQL) primary/standby |
| GaussDB(for MySQL)-MySQL 8.0 |
From the cloud | MySQL->MySQL |
|
|
From the cloud | DDS->MongoDB |
|
|
Self-built -> Self-built | MySQL->MySQL |
|
|
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.
Migration Direction | Data Flow | Full Migration | Full+Incremental Migration |
---|---|---|---|
To the cloud | MySQL->MySQL | Supported | Supported |
To the cloud | MySQL -> GaussDB(for MySQL) primary/standby | Supported | Supported |
To the cloud | MongoDB->DDS |
|
Note If you need to perform an incremental migration for a single-node instance, the source database must be the DDS single-node instance. |
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. |
Self-built -> Self-built | MySQL->MySQL | Supported | 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.
Network Type | Application Scenario | Preparations |
---|---|---|
VPC | Migrations between cloud databases in the same region |
|
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. |
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. |
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:
|
Migration Direction | Data Flow | VPC | Public Network | VPN or Direct Connect |
---|---|---|---|---|
To the cloud | MySQL->MySQL | Supported | Supported | Supported |
To the cloud | MySQL -> GaussDB(for MySQL) primary/standby | Supported | Supported | Supported |
To the cloud | MongoDB->DDS | Supported | Supported | Supported |
From the cloud | MySQL->MySQL | Supported | Supported | Supported |
From the cloud | DDS->MongoDB | Supported | Supported | Supported |
Self-built -> Self-built | MySQL->MySQL | Not supported | Supported | Supported |
Migration Objects¶
DRS allows you to migrate objects at different levels. The following table lists the 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 -> GaussDB(for MySQL) primary/standby | Supported | Supported | Supported |
To the cloud | MongoDB->DDS | Supported | Supported | Supported |
From the cloud | MySQL->MySQL | Supported | Supported | Supported |
From the cloud | DDS->MongoDB | Supported | Supported | Supported |
Self-built -> Self-built | MySQL->MySQL | Supported | Supported | Supported |
Advanced Features¶
DRS supports multiple features to ensure successful real-time migration.
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. |