Help Center/ Data Replication Service/ Service Overview/ Functions and Features/ Workload Replay
Updated on 2026-01-27 GMT+08:00
View PDF

Workload Replay

The following table lists the supported databases and versions.

Database Types

DRS supports workload replay management for the following types of databases.

Table 1 Database types

Replay Direction

Data Flow

Source DB

Destination DB

Destination DB Type

Current cloud

MySQL->MySQL

RDS for MySQL instances

RDS for MySQL instances
  • Single
  • Primary/Standby

Current cloud

MySQL->TaurusDB

RDS for MySQL instances

TaurusDB instances

Primary/Standby

Current cloud

TaurusDB->TaurusDB

TaurusDB instances

TaurusDB instances

Primary/Standby

Current cloud

TaurusDB->MySQL

TaurusDB instances

RDS for MySQL instances
  • Single
  • Primary/Standby

To the cloud

MySQL->MySQL
  • On-premises MySQL databases
  • ECS-hosted MySQL databases
  • MySQL databases on other clouds

RDS for MySQL instances
  • Single
  • Primary/Standby

To the cloud

MySQL->TaurusDB
  • On-premises MySQL databases
  • ECS-hosted MySQL databases
  • MySQL databases on other clouds

TaurusDB instances

Primary/Standby

To the cloud

Self-built MongoDB -> DDS

On-premises MongoDB

DDS instances
  • Cluster
  • Replica set
  • Single node

To the cloud

MariaDB->MySQL
  • On-premises MariaDB
  • ECS-hosted MariaDB
  • MariaDB on other clouds

RDS for MySQL instances

  • Basic edition TaurusDB instances
  • Single
  • Primary/Standby

To the cloud

MariaDB->MariaDB
  • On-premises MariaDB
  • ECS-hosted MariaDB
  • MariaDB on other clouds

RDS for MariaDB instances
  • Single
  • Primary/Standby

To the cloud

MariaDB->TaurusDB
  • On-premises MariaDB
  • ECS-hosted MariaDB
  • MariaDB on other clouds

TaurusDB instances

Primary/Standby

Database Versions

Table 2 Database versions

Replay Direction

Data Flow

Source DB Version

Destination DB Version

Current 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

Current cloud

MySQL->TaurusDB
  • MySQL 5.6.x
  • MySQL 5.7.x
  • MySQL 8.0.x

Compatible with MySQL 8.0

Current cloud

TaurusDB->TaurusDB

Compatible with MySQL 8.0

Compatible with MySQL 8.0

Current cloud

TaurusDB->MySQL

Compatible with MySQL 8.0
  • MySQL 5.6.x
  • MySQL 5.7.x
  • MySQL 8.0.x

To 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

To the cloud

MySQL->TaurusDB
  • MySQL 5.6.x
  • MySQL 5.7.x
  • MySQL 8.0.x

Compatible with MySQL 8.0

To the cloud

Self-built MongoDB -> DDS
  • On-premises MongoDB 5.0
  • On-premises MongoDB 6.0
  • On-premises MongoDB 7.0
  • DDS 4.4
  • DDS 5.0

To the cloud

MariaDB->MySQL
  • MariaDB 10.3
  • MariaDB 10.4
  • MariaDB 10.5
  • MySQL 5.6.x
  • MySQL 5.7.x
  • MySQL 8.0.x

To the cloud

MariaDB->MariaDB
  • MariaDB 10.3
  • MariaDB 10.4
  • MariaDB 10.5
  • MariaDB 10.5

To the cloud

MariaDB->TaurusDB
  • MariaDB 10.3
  • MariaDB 10.4
  • MariaDB 10.5

Compatible with MySQL 8.0

Network Types

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

Table 3 Network types

Network Type

Application Scenario

Preparations

VPC

Workload replay 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. 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

Workload replay 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 workload replay, ensure that the VPN network is accessible.

For more information about VPN, see Getting Started with Virtual Private Network.

Direct Connect

Workload replay 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

Workload replay from on-premises databases or other cloud databases to destination databases

To ensure network connectivity between the source and destination databases, perform the following operations:

  1. Enable public accessibility.

    Enable public accessibility for the source database based on your service requirements.

  2. Configure security group rules.
    • Add the EIPs of the DRS instance to the whitelist of the source database for inbound traffic.
    • If destination databases and the DRS 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 displayed on the Configure Source and Destination Databases page is the EIP of the DRS instance.
Table 4 Supported network types

Replay Direction

Source DB

Destination DB

VPC

Public Network

VPN or Direct Connect

Current cloud

MySQL

MySQL

Supported

Supported

Supported

Current cloud

MySQL

TaurusDB

Supported

Supported

Supported

Current cloud

TaurusDB

TaurusDB

Supported

Supported

Supported

Current cloud

TaurusDB

MySQL

Supported

Supported

Supported

To the cloud

MySQL

MySQL

Supported

Supported

Supported

To the cloud

MySQL

TaurusDB

Supported

Supported

Supported

To the cloud

Self-built MongoDB

DDS

Supported

Supported

Supported

To the cloud

MariaDB

MySQL

Supported

Supported

Supported

To the cloud

MariaDB

MariaDB

Supported

Supported

Supported

To the cloud

MariaDB

TaurusDB

Supported

Supported

Supported

Parent topic: Functions and Features