This topic describes the steps to create a data integration task for migration between ApsaraDB RDS for MySQL databases. The procedures of creating data integration tasks between other combinations of sources and targets are similar.

Prerequisites

The source and target ApsaraDB RDS for MySQL instances must reside in the supported regions, including China (Qingdao), China (Beijing), China (Zhangjiakou), China (Shenzhen), and China (Shanghai).

Background information

The process of creating a data integration task is similar to the process of creating a data migration task. Instead of executing the task immediately, you can specify a recurrence pattern for the migration task to recur at specified intervals.

Note If a source table does not include constraints that make sure that every record is unique, such as PRIMARY KEY constraints or UNIQUE constraints, duplicates may occur in the target database.

Access permissions

When migrating the definitions of views, stored procedures, and functions, DTS uses the user specified in the DEFINER attribute as the INVOKER attribute.

DTS does not migrate database accounts. After the migration, you must grant users the permissions to access the migrated views, stored procedures, and functions in the target database.

Procedure

  1. Log on to the Data Transmission Service console.
  2. In the left-side navigation pane, click Data Integration.
  3. In the region selector, select the region where the target database instance resides. For example, China (Qingdao).
  4. In the upper-right corner, click Create Data Integration Task.
  5. Complete the settings as follows:
    Section Parameter Description
    N/A Task Name DTS automatically generates a default task name. You can enter a name to describe the task. The name does not have to be unique for each task.
    Source Database Instance Type Select RDS Instance.
    Instance Region Select the region where the source ApsaraDB RDS for MySQL instance resides.
    RDS Instance ID Select the ID of the source ApsaraDB RDS for MySQL instance.
    Database Name Select the name of the source database on the ApsaraDB RDS for MySQL instance.
    Database Account Enter the database account on the source ApsaraDB RDS for MySQL instance.
    Database Password Enter the password of the database account. Click Test Connectivity next to Database Password to verify that the DTS server can connect to the specified database system using the specified connection settings, database account, and password.
    Encryption Select Non-encrypted or SSL-encrypted. If you want to select SSL-encrypted, you must enable SSL encryption for the RDS instance before you configure the data migration task. For more information, see Configure SSL encryption for an RDS MySQL instance.
    Destination Database Instance Type Select RDS Instance.
    Instance Region Select the region where the target ApsaraDB RDS for MySQL instance resides.
    RDS Instance ID Select the ID of the target ApsaraDB RDS for MySQL instance.
    Database Name Select the name of the target database on the ApsaraDB RDS for MySQL instance.
    Database Account Enter the database account on the target ApsaraDB RDS for MySQL instance.
    Database Password Enter the password of the database account. Click Test Connectivity next to Database Password to verify that the DTS server can connect to the specified database system using the specified connection settings, database account, and password.
    Encryption Select Non-encrypted or SSL-encrypted. If you want to select SSL-encrypted, you must enable SSL encryption for the RDS instance before you configure the data migration task. For more information, see Configure SSL encryption for an RDS MySQL instance.
  6. In the lower-right corner of the page, click Set Whitelist and Next.
  7. Complete the settings as follows:
    Setting Description
    Migration Types Select Schema Migration and Full Data Migration.
    Scheduler strategy Select an orchestration method. For example, Duplicate mode, create new full replica to target(create a new database every time).
    Dispatch effective date Select the start and end times of the effective period, and then click Confirm.
    Scheduling cycle Select a recurrence period. For a daily recurring schedule, select the number of days as the interval. For a weekly recurring schedule, select the days of the week on which you want the migration task to run. Then, enter a specific time of the day when the migration task will run.
    Task failure policy Specify how DTS will handle a failed migration. You can click View Scheduled Scheduling Time to preview the planned occurrences based on the specified schedule
    Available/Selected In the Available list, select the objects to be migrated, and then click the right arrow icon to add them into the Selected list.
  8. Click Precheck.
  9. After the precheck is passed, click Next.
  10. Follow the instructions to purchase an instance and complete the payment.