You can seamlessly migrate data between ApsaraDB for RDS instances.

Notes

  • The source and destination RDS instances must use the same database engines. DTS does not support data migration between RDS instances that use different database engines.
  • If the source database does not have primary keys or UNIQUE constraints, and fields are not required to be unique, duplicate data may exist in the destination database.
  • To ensure data consistency, do not write new data into the source RDS instance during full data migration.
  • DTS automatically resumes a failed data migration task. Before switching your workloads to the destination instance, you must stop or release the data migration task. Otherwise, the data from the source database will overwrite the data in the destination instance after the task is resumed.

Billing

Migration type Migration channel fee Public network traffic fee
Schema migration or full data migration Free of charge Migrating data from Alibaba Cloud over the Internet incurs fees. For more information, see Pricing.
Incremental data migration Billed. For more information, see Pricing.

Migration types

  • Schema migration

    DTS migrates the schemas of the required objects to the destination instance.

  • Full data migration

    DTS migrates historical data of the required objects from the source RDS instance to the destination RDS instance.

  • Incremental data migration

    After full data migration is complete, DTS synchronizes incremental data from the source RDS instance to the destination RDS instance. Incremental data migration helps you ensure service continuity when you migrate data between RDS instances.

Permissions required for database accounts

Database Schema migration Full data migration Incremental data migration
Source RDS instance The read/write permissions The read/write permissions The read/write permissions
Destination RDS instance The read/write permissions The read/write permissions The read/write permissions

Procedure

  1. Log on to the DTS console.
  2. In the left-side navigation pane, click Data Migration.
  3. At the top of the Migration Tasks page, select the region where the destination RDS instance resides.Select a region
  4. In the upper-right corner of the page, click Create Migration Task.
  5. Configure the information about the source and destination databases for the data migration task. Migrate data between RDS instances
    Section Parameter Description
    Task Name N/A DTS automatically generates a task name. We recommend that you use an informative name for easy identification. You do not need to use a unique task name.
    Source Database Instance Type Select RDS Instance.
    Instance Region Select the region where the destination RDS instance resides.
    RDS Instance ID Select the ID of the source RDS instance.
    Note The source and destination RDS instances can be the same or different. You can use DTS to migrate data within an RDS instance or between two RDS instances.
    Database Name Enter the name of the source database in the ApsaraDB RDS for PostgreSQL instance.
    Note This parameter is required only if the database engine of the RDS instance is PostgreSQL.
    Database Account Enter the database account of the source RDS instance. For more information about permissions required for the account, see Permissions required for database accounts.
    Database Password Enter the password for the database account.
    Note After the source database parameters are specified, click Test Connectivity next to the Database Password parameter to verify whether the specified parameters are correct. If the source database parameters are correct, the Test Passed message is displayed, If the Test Failed message is displayed, click Diagnose in the Test Failed message. Modify the source database parameters as prompted.
    Encryption Select Non-encrypted or SSL-encrypted. If you want to select SSL-encrypted, you must enable SSL encryption for the RDS instance before configuring the data migration task. For more information, see Configure SSL encryption for an RDS for MySQL instance.
    Note

    This parameter is required only if the database engine of the RDS instance is MySQL.

    The Encryption parameter is available only in mainland China and Hong Kong(China).

    Destination Database Instance Type Select RDS Instance.
    Instance Region Select the region where the destination RDS instance resides.
    RDS Instance ID Select the ID of the destination RDS instance.
    Note The source and destination RDS instances can be the same or different. You can use DTS to migrate data within an RDS instance or between two RDS instances.
    Database Name Enter the name of the destination database in the ApsaraDB RDS for PostgreSQL instance. The name of the destination database can be different from that of the source database.
    Note This parameter is required only if the database engine of the RDS instance is PostgreSQL.
    Database Account Enter the database account of the destination RDS instance. For more information about permissions required for the account, see Permissions required for database accounts.
    Database Password Enter the password for the database account.
    Note After the destination database parameters are specified, click Test Connectivity next to the Database Password parameter to verify whether the specified parameters are correct. If the destination database parameters are correct, the Test Passed message is displayed. If the Test Failed message is displayed, click Diagnose in the Test Failed message. Modify the destination database parameters as prompted.
    Encryption Select Non-encrypted or SSL-encrypted. If you want to select SSL-encrypted, you must enable SSL encryption for the RDS instance before configuring the data migration task. For more information, see Configure SSL encryption for an RDS for MySQL instance.
    Note

    This parameter is required only if the database engine of the RDS instance is MySQL.

    The Encryption parameter is available only in mainland China and Hong Kong(China).

  6. In the lower-right corner of the page, click Set Whitelist and Next.
    Note The CIDR blocks of DTS servers are automatically added to the whitelist of the source and destination RDS instances. This ensures that DTS servers can connect to the RDS instances.
  7. Select the migration types and objects to be migrated. Select the migration types and objects to be migrated
    Parameter Description
    Migration types

    Select the migration types based on your requirements. The migration types must be supported by the database engine.

    • To perform only full data migration, select Schema Migration and Full Data Migration.
      Note To ensure data consistency, do not write new data into the source RDS instance during full data migration.
    • To migrate data with minimal downtime, you must select Schema Migration, Full Data Migration, and Incremental Data Migration.
    Objects to be migrated

    In the Available section, select the objects to be migrated and click the Right arrow icon to add the objects to the Selected section.

    Note
    • You can select databases, tables, or columns as the objects to be migrated.
    • After an object is migrated to the destination RDS instance, the name of the object remains the same as that in the source RDS instance. If the migrated object has a different name in the destination RDS instance, you can use the object name mapping feature provided by DTS. For more information about how to use this feature, see Object name mapping.
    • If you use the object name mapping feature on an object, other objects that are dependent on the object may fail to be migrated.
  8. Click Precheck in the lower-right corner of the page.
    Note
    • A precheck is performed for a data migration task. A data migration task can be started only if it passes the precheck.
    • If the precheck fails, click Note corresponding to each failed item to view the details. Fix the problems as instructed and run the precheck again.
  9. After the precheck is passed, click Next.
  10. On the Confirm Settings dialog box that appears, specify Channel Specification and select the Data Transmission Service (Pay-As-You-Go) Service Terms.
  11. Click Buy and Start to start the data migration task.
    • Full data migration

      Do not manually stop a migration task. Otherwise, data migrated to the destination database will be incomplete. Wait until the data migration task stops when it is complete.

    • Incremental data migration

      An incremental data migration task does not automatically end. You must manually end the migration task.

      Note Select an appropriate time point to manually end the migration task. For example, you can end the migration task during off-peak hours or before you switch your workloads to the destination instance.
      1. When the task progress bar switches to Incremental Data Migration and The migration task is not delayed appears, stop writing new data to the source database for a few minutes. Then, the progress bar will show the latency of the incremental data migration.
      2. When the status of incremental data migration changes to The migration task is not delayed, manually stop the migration task.The migration task is not delayed