Configure a data synchronization task (new console)

更新时间:
复制 MD 格式

DTS data synchronization lets you set up synchronization tasks in a few steps through the new console.

Usage notes

This topic covers the general data synchronization procedure. Steps may vary by topology. Topology-specific instructions are in Overview of data synchronization scenarios.

Note

This topic uses a one-way synchronization between RDS for MySQL instances (configured before purchase) as an example. Actual console parameters may differ.

Prerequisites

  • If the source or destination is a self-managed database, complete the Preparations to meet DTS environment requirements.

  • Create source and destination database instances supported by DTS. Supported databases and versions are listed in Overview of data synchronization scenarios.

Procedure

  1. Go to the data synchronization task list page in the destination region. You can do this in one of two ways.

    DTS console

    1. Log on to the DTS console.

    2. In the navigation pane on the left, click Data Synchronization.

    3. In the upper-left corner of the page, select the region where the synchronization instance is located.

    DMS console

    Note

    The actual steps may vary depending on the mode and layout of the DMS console. For more information, see Simple mode console and Customize DMS console layout and style.

    1. Log on to the DMS console.

    2. In the top menu bar, choose Data + AI > DTS (DTS) > Data Synchronization.

    3. To the right of Data Synchronization Tasks, select the region of the synchronization instance.

  2. Click Create Task to open the task configuration page.

  3. Optional: In the upper-right corner of the page, click New Configuration Page.

    Note
    • If you are already on the new configuration page (the button in the upper-right corner is Back to Previous Version), you can skip this step.

    • Some parameters differ between the new and old configuration pages. We recommend using the new version.

  4. Configure the source and destination databases.

    Warning

    After you select the source and destination instances, review the Limits at the top of the page. Otherwise, the task may fail or data inconsistency may occur.

    Category

    Configuration

    Description

    None

    Task Name

    DTS automatically generates a task name. We recommend that you specify a descriptive name for easy identification. The name does not need to be unique.

    Source Database

    Select Existing Connection

    For this example, leave this blank and enter the database details below.

    Database Type

    Select MySQL.

    Access Method

    Select Alibaba Cloud Instance.

    Instance Region

    Select the region of the source ApsaraDB RDS for MySQL instance.

    Replicate Data Across Alibaba Cloud Accounts

    For this example, select No, as the database instance belongs to the current Alibaba Cloud account.

    RDS Instance ID

    Select the ID of the source ApsaraDB RDS for MySQL instance.

    Database Account

    Enter the database account of the source ApsaraDB RDS for MySQL instance. The account requires REPLICATION CLIENT, REPLICATION SLAVE, and SELECT permissions on the objects to synchronize.

    Database Password

    Enter the password for the specified database account.

    Encryption

    For this example, keep the default selection.

    Destination Database

    Select Existing Connection

    For this example, leave this blank and enter the database details below.

    Database Type

    Select MySQL.

    Access Method

    Select Alibaba Cloud Instance.

    Instance Region

    Select the region of the destination ApsaraDB RDS for MySQL instance.

    Replicate Data Across Alibaba Cloud Accounts

    For this example, select No, as the database instance belongs to the current Alibaba Cloud account.

    RDS Instance ID

    Select the ID of the destination ApsaraDB RDS for MySQL instance.

    Database Account

    Enter the database account of the destination ApsaraDB RDS for MySQL instance. The account must have read and write permissions.

    Database Password

    Enter the password for the specified database account.

    Encryption

    For this example, keep the default selection.

  5. After completing the configuration, click Test Connectivity and Proceed at the bottom of the page.

    Note
    • Ensure that you add the CIDR blocks of the DTS servers (either automatically or manually) to the security settings of both the source and destination databases to allow access. For more information, see Add the IP address whitelist of DTS servers.

    • If the source or destination is a self-managed database (i.e., the Access Method is not Alibaba Cloud Instance), you must also click Test Connectivity in the CIDR Blocks of DTS Servers dialog box.

  6. Configure the task objects.

    1. On the Configure Objects page, specify the objects to synchronize.

      In this example, select Schema Synchronization, Full Data Synchronization, and Incremental Data Synchronization under Synchronization Types. In the Source Objects box select the objects to synchronize. Keep the defaults or adjust as needed.

      Parameter description

      Configuration

      Description

      Synchronization Types

      DTS always selects Incremental Data Synchronization. By default, you must also select Schema Synchronization and Full Data Synchronization. After the precheck, DTS initializes the destination cluster with the full data of the selected source objects, which serves as the baseline for subsequent incremental synchronization.

      Method to Migrate Triggers in Source Database

      Select a trigger synchronization method. Skip this if no triggers are involved. Configure a method to synchronize or migrate triggers.

      Note

      This parameter is available only if Schema Synchronization is selected under Synchronization Types.

      Enable Migration Assessment

      Specify whether to assess if source and destination database schemas (index length, stored procedures, table dependencies) meet synchronization requirements. Select Yes or No.

      Note
      • This parameter is available only if Schema Synchronization is selected under Synchronization Types.

      • Selecting Yes extends the precheck duration. View Assessment Result during the precheck. Evaluation results do not affect precheck results.

      Synchronization Topology

      Select One-way Synchronization.

      Processing Mode of Conflicting Tables

      • Precheck and Report Errors: Checks for tables with the same names in the destination database. If any tables with the same names are found, an error is reported during the precheck and the data synchronization task does not start. Otherwise, the precheck is successful.

        Note

        If you cannot delete or rename the table with the same name in the destination database, you can map it to a different name in the destination. For more information, see Object name mapping.

      • Ignore Errors and Proceed: Skips the check for tables with the same name in the destination database.

        Warning

        Selecting Ignore Errors and Proceed may cause data inconsistency and put your business at risk. For example:

        • If the table schemas are consistent and a record in the destination database has the same primary key or unique key value as a record in the source database:

          • During full data synchronization, DTS retains the destination record and skips the source record.

          • During incremental synchronization, DTS overwrites the destination record with the source record.

        • If the table schemas are inconsistent, data initialization may fail. This can result in only partial data synchronization or a complete synchronization failure. Use with caution.

      Capitalization of Object Names in Destination Instance

      Configure the case-sensitivity policy for database, table, and column names in the destination instance. By default, the DTS default policy is selected. You can also choose to use the default policy of the source or destination database. For more information, see Case policy for destination object names.

      Source Objects

      In the Source Objects box, click the objects, and then click 向右 to move them to the Selected Objects box.

      Note

      You can select objects at the database, table, or column level. If you select only tables or columns, DTS does not synchronize other object types (such as views, triggers, and stored procedures).

      Selected Objects

      • To rename a single object in the destination instance, right-click the object in the Selected Objects box. For more information, see Map a single object name.

      • To rename multiple objects in bulk, click Batch Edit in the upper-right corner of the Selected Objects box. For more information, see Map multiple object names in bulk.

      Note
      • To select SQL operations (DML/DDL) to synchronize, right-click the object in the Selected Objects box and select the operations.

      • To filter data using a WHERE clause, right-click a table in the Selected Objects box and define the filter condition. For more information, see Set filter conditions.

    2. Click Next: Advanced Settings.

      In this example, keep the defaults or configure as needed.

      Parameter description

      Configuration

      Description

      Dedicated Cluster for Task Scheduling

      By default, DTS uses a shared cluster for tasks, so you do not need to make a selection. For greater task stability, you can purchase a dedicated cluster to run the DTS synchronization task. For more information, see What is a DTS dedicated cluster?.

      Copy the temporary table of the Online DDL tool that is generated in the source table to the destination database.

      If the source database uses Data Management (DMS) or gh-ost for online DDL changes, choose whether to synchronize the temporary tables generated during these operations.

      Important

      DTS tasks do not currently support online DDL changes performed by tools like pt-online-schema-change. Using such tools will cause the DTS task to fail.

      • Yes: Synchronizes the temporary tables generated by online DDL changes.

        Note

        If the data of temporary tables generated by online DDL changes is too large, it may cause synchronization latency.

      • No, Adapt to DMS Online DDL: Does not synchronize temporary tables generated by online DDL changes. Instead, it synchronizes only the original DDL statements executed in Data Management (DMS).

        Note

        This approach will cause table locks on the destination database.

      • No, Adapt to gh-ost: Does not the synchronize temporary tables generated by online DDL changes. Instead, it synchronizes only the original DDL statements executed by gh-ost. You can use default or custom regular expressions for gh-ost shadow and trash tables.

        Note

        This approach will cause table locks on the destination database.

      Whether to Migrate Accounts

      Select whether to synchronize the account information from the source database. If you select Yes, you must also select the accounts to synchronize and confirm their permissions. For more information about authorization methods, see Migrate database accounts.

      Retry Time for Failed Connections

      If the connection to the source or destination database fails after the synchronization task starts, DTS reports an error and immediately begins to retry the connection. The default retry duration is 720 minutes. You can customize the retry time to a value from 10 to 1,440 minutes. We recommend a duration of 30 minutes or more. If the connection is restored within this period, the task resumes automatically. Otherwise, the task fails.

      Note
      • If multiple DTS instances (e.g., Instance A and B) share a source or destination, DTS uses the shortest configured retry duration (e.g., 30 minutes for A, 60 for B, so 30 minutes is used) for all instances.

      • DTS charges for task runtime during connection retries. Set a custom duration based on your business needs, or release the DTS instance promptly after you release the source/destination instances.

      Retry Time for Other Issues

      If a non-connection issue (e.g., a DDL or DML execution error) occurs, DTS reports an error and immediately retries the operation. The default retry duration is 10 minutes. You can also customize the retry time to a value from 1 to 1,440 minutes. We recommend a duration of 10 minutes or more. If the related operations succeed within the set retry time, the synchronization task automatically resumes. Otherwise, the task fails.

      Important

      The value of Retry Time for Other Issues must be less than that of Retry Time for Failed Connections.

      Enable Throttling for Full Data Synchronization

      During full data synchronization, DTS consumes read and write resources from the source and destination databases, which can increase their load. To mitigate pressure on the destination database, you can limit the migration rate by setting Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s).

      Note

      Enable Throttling for Incremental Data Synchronization

      You can also limit the incremental synchronization rate to reduce pressure on the destination database by setting RPS of Incremental Data Synchronization and Data synchronization speed for incremental synchronization (MB/s).

      Environment Tag

      Select an environment tag to identify the instance.

      Whether to delete SQL operations on heartbeat tables of forward and reverse tasks

      Choose whether DTS writes heartbeat SQL information to the source database while the instance is running.

      • Yes: Does not write heartbeat SQL information to the source database. The DTS instance may display latency.

      • No: Writes heartbeat SQL information to the source database. This may interfere with source database operations like physical backups and cloning.

      Configure ETL

      Choose whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values:

      Monitoring and Alerting

      Choose whether to set up alerts. If the synchronization fails or the latency exceeds the specified threshold, DTS sends a notification to the alert contacts.

    3. Click Data Verification to configure a data verification task.

      To use the data verification feature, see Configure data verification.

  7. Save the task and perform a precheck.

    • To view the parameters for configuring this instance via an API operation, hover over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the tooltip.

    • If you have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.

    Note
    • Before a synchronization task starts, DTS performs a precheck. You can start the task only if the precheck passes.

    • If the precheck fails, click View Details next to the failed item, fix the issue as prompted, and then rerun the precheck.

    • If the precheck generates warnings:

      • For non-ignorable warning, click View Details next to the item, fix the issue as prompted, and run the precheck again.

      • For ignorable warnings, you can bypass them by clicking Confirm Alert Details, then Ignore, and then OK. Finally, click Precheck Again to skip the warning and run the precheck again. Ignoring precheck warnings may lead to data inconsistencies and other business risks. Proceed with caution.

  8. Purchase the instance.

    1. When the Success Rate reaches 100%, click Next: Purchase Instance.

    2. On the Purchase page, select the billing method and link specifications for the data synchronization instance. For more information, see the following table.

      Category

      Parameter

      Description

      New Instance Class

      Billing Method

      • Subscription: You pay upfront for a specific duration. This is cost-effective for long-term, continuous tasks.

      • Pay-as-you-go: You are billed hourly for actual usage. This is ideal for short-term or test tasks, as you can release the instance at any time to save costs.

      Resource Group Settings

      The resource group to which the instance belongs. The default is default resource group. For more information, see What is Resource Management?.

      Instance Class

      DTS offers synchronization specifications at different performance levels that affect the synchronization rate. Select a specification based on your business requirements. For more information, see Data synchronization link specifications.

      Subscription Duration

      In subscription mode, select the duration and quantity of the instance. Monthly options range from 1 to 9 months. Yearly options include 1, 2, 3, or 5 years.

      Note

      This option appears only when the billing method is Subscription.

    3. Read and select the checkbox for Data Transmission Service (Pay-as-you-go) Service Terms.

    4. Click Buy and Start, and then click OK in the OK dialog box.

      You can monitor the task progress on the data synchronization page.