This topic provides an overview of the data restoration, migration, and synchronization solutions supported by ApsaraDB RDS for MySQL.

Comparison

  • Comparison between data restoration and migration

    Although data restoration and migration can both be used to replicate data to a new RDS instance, they differ in the following aspects:

    • The data restoration feature enables you to restore data from a data backup file, and restore data from a specific point in time by using a data backup file and a binary log file.
    • The data migration feature enables you to use Alibaba Cloud Data Transmission Service (DTS) to migrate data from an on-premises database, a user-created database on an ECS instance, or a database on a third-party cloud platform to Alibaba Cloud. This feature also enables you to migrate data from Alibaba Cloud to a user-created database.

    You can use data restoration and migration together to meet more business needs. For example, you can restore data to a new RDS instance and then use DTS to migrate the data back to its original RDS instance. This way, you do not need to update the endpoints on your application.

    Note The data restoration feature provided in the ApsaraDB for RDS console can meet most business needs for data restoration and some business needs for data migration. However, it does not support incremental data migration.
  • Comparison between data migration and synchronization
    • The data migration feature is used to migrate data to Alibaba Cloud. If you select the incremental data migration option when you create a migration task, the data updated in the original RDS instance is synchronized to the new RDS instance. However, this feature is different from the data synchronization feature, which supports more functions such as online updates of synchronized objects and two-way data synchronization. After a data migration task is complete, you can release it.
    • The data synchronization feature is used to synchronize data between two data sources in real time. It is suitable for diversified scenarios such as active geo-redundancy, disaster recovery, cross-border data synchronization, query load balancing, cloud BI systems, and real-time data warehousing. After you create a data synchronization task, it keeps synchronizing data between the specified data sources to ensure data consistency.

Data restoration

Scenario Reference
Restore the data of an ApsaraDB RDS for MySQL database to its original instance or to a new instance
Restore the data of an ApsaraDB RDS for MySQL database to a user-created database
Note If the original instance is not released or you do not want to restore data from a specific point in time, we recommend that you use DTS to migrate the data from your ApsaraDB for MySQL database to a user-created MySQL database.

Data migration

Scenario Reference
Migrate data from an ApsaraDB RDS for MySQL instance to a PolarDB cluster
Migrate data from a user-created database to an ApsaraDB RDS for MySQL instance
Migrate data from a database on a third-party cloud platform to an ApsaraDB RDS for MySQL instance
Migrate data between databases within an ApsaraDB RDS for MySQL instance Migrate data between databases with different names in the same instance
Migrate data from an ApsaraDB RDS for MySQL instance to a user-created MySQL database Migrate data from an ApsaraDB RDS for MySQL database to a user-created MySQL database

Data synchronization

Scenario Reference
Synchronize data between ApsaraDB RDS for MySQL instances
Synchronize data from an ApsaraDB RDS for MySQL instance to other types of databases

Synchronize data from ApsaraDB RDS for MySQL to MaxCompute