Promo Center

50% off for new user

Direct Mail-46% off

Learn More

Configure two-way data synchronization between ApsaraDB RDS for PostgreSQL instances

Updated at: 2025-02-18 03:50
important

This topic contains important information on necessary precautions. We recommend that you read this topic carefully before proceeding.

Data Transmission Service (DTS) supports two-way data synchronization between two PostgreSQL databases, such as databases in ApsaraDB RDS for PostgreSQL instances and self-managed PostgreSQL databases. This feature applies to scenarios such as active geo-redundancy (unit-based) and geo-disaster recovery. This topic describes how to configure two-way data synchronization between ApsaraDB RDS for PostgreSQL instances.

Prerequisites

Limits

Category

Description

Category

Description

Limits on the source and destination databases

  • If the tables to be synchronized do not have primary keys and UNIQUE constraints, you must enable the Exactly-Once write feature when you configure the data synchronization task. Otherwise, the destination database may contain duplicate data records. For more information, see Synchronize tables without primary keys or UNIQUE constraints.

  • If you select tables as the objects to be synchronized and you want to edit the tables, such as renaming tables or columns in the destination database, you can synchronize up to 5,000 tables in a single data synchronization task. If you run a task to synchronize more than 5,000 tables, a request error occurs. In this case, we recommend that you configure multiple tasks to synchronize the tables or configure a task to synchronize the entire database.

  • DTS cannot synchronize temporary tables in source database, internal triggers, or some internal procedures and functions written in the C programming language. DTS can synchronize custom parameters of the COMPOSITE, ENUM, and RANGE types. The tables to be synchronized must have the PRIMARY KEY, FOREIGN KEY, UNIQUE, or CHECK constraints.

  • The following requirements for WAL logs must be met:

    • The value of the wal_level parameter must be logical.

    • If you perform only incremental data synchronization, the WAL logs of the source database must be stored for more than 24 hours. If you perform both full data synchronization and incremental data synchronization, the WAL logs of the source database must be stored for at least seven days. Otherwise, DTS may fail to obtain the WAL logs and the task may fail. In exceptional circumstances, data inconsistency or loss may occur. After full data synchronization is complete, you can set the retention period to more than 24 hours. Make sure that you set the retention period of WAL logs based on the preceding requirements. Otherwise, service reliability or performance in the Service Level Agreement (SLA) of DTS may not be guaranteed.

  • Limits on operations to be performed on the source database:

    • If you want to perform a primary/secondary switchover on the source ApsaraDB RDS for PostgreSQL instance, the Logical Replication Slot Failover feature must be enabled. This prevents logical subscriptions from being interrupted and ensures that your data synchronization task can run as expected. For more information, see Logical Replication Slot Failover.

    • The logical subscription from source database has limits on the usage of DTS. If the size of a single data to be synchronized from the source database exceeds 256 MB upon incremental data changes, the data synchronization instance that is running fails to run and cannot be recovered. You need to configure the task again.

    • During schema synchronization and full data synchronization, do not execute DDL statements to change the schemas of databases or tables. Otherwise, the data synchronization task fails.

  • If the source database has long-running transactions and incremental data is synchronized in the data synchronization task, the write-ahead logging (WAL) logs generated before the long-running transactions in the source database are committed may be accumulated. As a result, the disk space of the source database may be insufficient.

  • If a major version upgrade for the source database of a data synchronization instance that is running is performed, the instance fails to run and cannot be recovered. You need to configure the task again.

Other limits

  • A data synchronization task can synchronize data from only one database. To synchronize data from multiple databases, you must create a data synchronization task for each database.

  • DTS cannot synchronize tables that have inheritance relationships across schemas.

  • During data synchronization, if you select a schema as the object to synchronize, take note of the following limits: If you create a table in the schema or run the RENAME command to rename the table, you must execute the ALTER TABLE schema.table REPLICA IDENTITY FULL; statement before you write data to the table. This ensures data consistency. When you execute this statement, we recommend that you do not lock the table. Otherwise, a deadlock occurs.

    Note
    • Replace the schema and table in the preceding sample statement with the actual schema name and table name.

    • We recommend that you perform this operation during off-peak hours.

  • DTS does not check the validity of metadata, such as sequences. You must manually check the validity of metadata.

  • After your workloads are switched to the destination database, new sequences do not increment from the maximum value of the sequences in the source database. Therefore, you must query the maximum value of the sequences in the source database before you switch your workloads to the destination database. Then, you must specify the queried maximum value as the starting value of the sequences in the destination database. You can run the following statements to query the maximum value of the sequences in the source database:

    do language plpgsql $$
    declare
      nsp name;
      rel name;
      val int8;
    begin
      for nsp,rel in select nspname,relname from pg_class t2 , pg_namespace t3 where t2.relnamespace=t3.oid and t2.relkind='S'
      loop
        execute format($_$select last_value from %I.%I$_$, nsp, rel) into val;
        raise notice '%',
        format($_$select setval('%I.%I'::regclass, %s);$_$, nsp, rel, val+1);
      end loop;
    end;
    $$;
    Note

    The returned SQL statements contain all sequences in the source database. You can perform operations in the destination database based on your business requirements.

  • DTS creates the following temporary tables in the source database to obtain the DDL statements of incremental data, the schemas of incremental tables, and the heartbeat information. During data synchronization, do not delete temporary tables in the source database. Otherwise, the data synchronization task fails. After the DTS instance is released, temporary tables are automatically deleted.

    public.dts_pg_class, public.dts_pg_attribute, public.dts_pg_type, public.dts_pg_enum, public.dts_postgres_heartbeat, public.dts_ddl_command, and public.dts_args_session.

  • To ensure that the latency of data synchronization is accurate, DTS adds a heartbeat table to the source database. The name of the heartbeat table is dts_postgres_heartbeat.

  • During data synchronization, DTS creates a replication slot for the source database. The replication slot is prefixed with dts_sync_. DTS can obtain the incremental logs of the source database within the last 15 minutes by using this replication slot.

    Note
    • After the DTS instance is released, the replication slot is automatically deleted. If you change the password of the source database or delete the IP addresses of DTS from the IP address whitelist, the replication slot cannot be automatically deleted. In this case, you must delete the replication slot in the source database to prevent the replication slot from piling up.

    • If the data synchronization task is released or fails, DTS automatically deletes the replication slot. If a primary/secondary switchover is performed on the source PostgreSQL database, you must log on to the secondary database to delete the replication slot.

    Amazon slot查询信息

  • Before you synchronize data, evaluate the impact of data synchronization on the performance of the source and destination databases. We recommend that you synchronize data during off-peak hours. During initial full data synchronization, DTS uses the read and write resources of the source and destination databases. This may increase the loads on the database servers.

  • During initial full data synchronization, concurrent INSERT operations cause fragmentation in the tables of the destination database. Therefore, after initial full data synchronization is complete, the size of the used tablespace of the destination database is larger than that of the source database.

  • If you use only DTS to write table data to the destination database, you can use DMS to perform online DDL operations on source tables during data synchronization. For more information, see Change schemas without locking tables.

  • Data inconsistency between the source and destination databases occurs if data from other sources is written to the destination database during the data synchronization. For example, if you use DMS to execute online DDL statements while data from other sources is written to the destination database, data loss may occur in the destination database.

  • If you use a privileged account or superuser account as the destination database account to perform full data synchronization or incremental data synchronization, and the tables to be synchronized contain foreign keys, triggers, or event triggers, DTS temporarily sets the session_replication_role parameter to replica at the session level. If the destination database account does not have the required permissions, you must manually set the session_replication_role parameter to replica. If the value of the session_replication_role parameter is replica and you perform the cascade update or delete operations on the source database during full data synchronization or incremental data synchronization, data inconsistency may occur. After the data synchronization task is released, you can change the value of the session_replication_role parameter back to origin.

  • A two-way data synchronization instance contains a forward synchronization task and a reverse synchronization task. If an object is to be synchronized in both the forward and reverse synchronization tasks when you configure or reset the instance, the following rules apply:

    • Only one of the tasks can synchronize both the full data and incremental data of objects. The other task synchronizes only the incremental data of the objects.

    • The source data of the current task can be synchronized only to the destination database in the task. The synchronized data is not used as the source data of the other task.

  • If a DTS task fails to run, DTS technical support will try to restore the task within 8 hours. During the restoration, the task may be restarted, and the parameters of the task may be modified.

    Note

    Only the parameters of the task may be modified. The parameters of databases are not modified. The parameters that may be modified include but are not limited to the parameters in the "Modify instance parameters" section of the Modify the parameters of a DTS instance topic.

Special cases

  • If the source database is an ApsaraDB RDS for PostgreSQL instance, take note of the following limits:

    During data synchronization, do not modify the endpoint and zone of the ApsaraDB RDS for PostgreSQL instance. Otherwise, the data synchronization task fails.

  • If the source database is a self-managed PostgreSQL database, take note of the following limits:

    The values of the max_wal_senders and max_replication_slots parameters must be greater than the sum of the following numbers: the number of used replication slots in the self-managed PostgreSQL database and the number of DTS instances that must be created to synchronize data from this database.

  • If the source database is a Cloud SQL for PostgreSQL instance provided by Google Cloud Platform, you must set the Database Account parameter to a database account with the cloudsqlsuperuser permission for the source database. When you select the objects to be synchronized, you must select the objects that the specified account is authorized to manage. Otherwise, you must grant the OWNER permission on the selected objects to the specified account.

    Note

    An account with the cloudsqlsuperuser permission cannot manage the data that is owned by other accounts that have the cloudsqlsuperuser permission.

Billing

Synchronization typeTask configuration fee
Synchronization typeTask configuration fee
Schema synchronization and full data synchronizationFree of charge.
Incremental data synchronizationCharged. For more information, see Billing overview.

Supported synchronization topologies

DTS supports two-way data synchronization only between two PostgreSQL databases. DTS does not support two-way data synchronization between multiple PostgreSQL databases.

Conflict detection

To ensure data consistency, make sure that data records with the same primary key, business primary key, or unique key are updated only on one of the synchronization nodes. If data records are updated on both nodes, DTS responds to conflicts based on the conflict resolution policy that you specify for the data synchronization task.

DTS checks and fixes conflicts to maximize the stability of two-way synchronization instances. DTS can detect the following types of conflicts:

  • Uniqueness conflicts caused by INSERT operations

    INSERT operations that do not comply with the uniqueness constraint cannot be synchronized. For example, if a record with the same primary key value is inserted into the two synchronization nodes at almost the same time, one of the inserted records fails to be synchronized. The synchronization fails because a record with the same primary key value already exists on the other node.

  • Inconsistent records caused by UPDATE operations

    • If the records to be updated do not exist in the destination instance, DTS converts the UPDATE operation into an INSERT operation. However, uniqueness conflicts may occur.

    • The primary keys or unique keys of the records to insert may conflict with those of existing records in the destination instance.

  • Non-existent records to be deleted

    The records to be deleted do not exist in the destination instance. In this case, DTS ignores the DELETE operation regardless of the conflict resolution policy that you specify.

Important
  • During two-way synchronization, the system time of the source and destination instances may be different. Synchronization latency may occur. For these reasons, DTS does not ensure that the conflict detection mechanism can prevent all data conflicts. To perform two-way synchronization, make sure that records with the same primary key, business primary key, or unique key are updated only on one of the synchronization nodes.

  • DTS provides conflict resolution policies to prevent conflicts that may occur during data synchronization. You can select a conflict resolution policy when you configure two-way data synchronization.

Supported objects to be synchronized

  • SCHEMA and TABLE.

    Note

    Including PRIMARY KEY, UNIQUE KEY, FOREIGN KEY, DATATYPE (built-in data type), and DEFAULT CONSTRAINT.

  • VIEW, PROCEDURE (PostgreSQL V11 or later.), FUNCTION, RULE, SEQUENCE, EXTENSION, TRIGGER, AGGREGATE, INDEX, OPERATOR, and DOMAIN.

SQL operations that can be synchronized

Operation type

SQL statement

Operation type

SQL statement

DML

INSERT, UPDATE, and DELETE

DDL

  • DDL operations can be synchronized only by data synchronization tasks that are created after October 1, 2020.

    Important
  • If the database account of the source database is a privileged account and the minor engine version of the ApsaraDB RDS for PostgreSQL instance is 20210228 or later, DTS can synchronize the following DDL statements. For information about how to update the minor engine version of an instance, see Update the minor engine version.

    • CREATE TABLE and DROP TABLE

    • ALTER TABLE, including RENAME TABLE, ADD COLUMN, ADD COLUMN DEFAULT, ALTER COLUMN TYPE, DROP COLUMN, ADD CONSTRAINT, ADD CONSTRAINT CHECK, and ALTER COLUMN DROP DEFAULT

    • TRUNCATE TABLE (The version of the source self-managed PostgreSQL database must be 11 or later.)

    • CREATE INDEX ON TABLE

    Important
    • You cannot synchronize additional information of DDL statements, such as CASCADE or RESTRICT.

    • You cannot synchronize the DDL statements from a session that executes the SET session_replication_role = replica statement.

    • You cannot synchronize DDL statements that are executed by invoking functions.

    • If multiple SQL statements committed by the source database at the same time contain both DML and DDL statements, DTS does not synchronize the DDL statements.

    • If multiple SQL statements committed by the source database at the same time contain DDL statements for objects that are not synchronized, the DDL statements are not synchronized.

Important

DDL operations can be synchronized only in the forward direction from the source database to the destination database. DDL operations cannot be synchronized from the destination database to the source database because DDL operations are ignored in the reverse direction.

Procedure

  1. Purchase an instance for two-way data synchronization. For more information, see Purchase a DTS instance.

    Important

    On the buy page, set both the Source Instance and Destination Instance parameters to PostgreSQL and set the Synchronization Topology parameter to Two-way Synchronization.

  2. Go to the Data Synchronization page of the new DTS console.

    Note

    You can also log on to the Data Management (DMS) console. In the top navigation bar, move the pointer over Data Development and choose DTS (DTS) > Data Synchronization.

  3. In the upper-left corner of the page, select the region in which the purchased data synchronization instance resides.

  4. Find the data synchronization instance and click Configure Task in the Actions column of the first data synchronization task.

  5. Configure the source and destination databases. The following table describes the parameters.

    Warning

    After you configure the source and destination databases, we recommend that you read the Limits that are displayed on the page. Otherwise, the task may fail or data inconsistency may occur.

    Section

    Parameter

    Description

    Section

    Parameter

    Description

    N/A

    Task Name

    The name of the DTS task. DTS automatically generates a task name. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to specify a unique task name.

    Source Database

    Database Type

    The type of the source database. Select PostgreSQL.

    Access Method

    The access method of the source database. Select Alibaba Cloud Instance.

    Instance Region

    The source region that you selected on the buy page. You cannot modify this parameter.

    Instance ID

    The ID of the source ApsaraDB RDS for PostgreSQL instance.

    Database Name

    The name of the source database in the source ApsaraDB RDS for PostgreSQL instance.

    Database Account

    A privileged account of the source ApsaraDB RDS for PostgreSQL instance. The account must be the owner of the source database. For more information about how to create an account for an ApsaraDB RDS for PostgreSQL instance and grant permissions to this account, see Create an account and Create a database.

    Database Password

    The password that is used to access the database.

    Encryption

    Specifies whether to encrypt the connection to the source database. You can configure this parameter based on your business requirements. In this example, Non-encrypted is selected.

    If you want to establish an SSL-encrypted connection to the source database, perform the following steps: Select SSL-encrypted, upload CA Certificate, Client Certificate, and Private Key of Client Certificate as needed, and then specify Private Key Password of Client Certificate.

    Note
    • If you set Encryption to SSL-encrypted for a self-managed PostgreSQL database, you must upload CA Certificate.

    • If you want to use the client certificate, you must upload Client Certificate and Private Key of Client Certificate and specify Private Key Password of Client Certificate.

    • For information about how to configure SSL encryption for an ApsaraDB RDS for PostgreSQL instance, see SSL encryption.

    Destination Database

    Database Type

    The type of the destination database. Select PostgreSQL.

    Access Method

    The access method of the destination database. Select Alibaba Cloud Instance.

    Instance Region

    The destination region that you selected on the buy page. You cannot modify this parameter.

    Instance ID

    The ID of the destination ApsaraDB RDS for PostgreSQL instance.

    Database Name

    The name of the destination database in the destination ApsaraDB RDS for PostgreSQL instance.

    Database Account

    A privileged account of the destination ApsaraDB RDS for PostgreSQL instance. The account must be the owner of the destination database. For more information about how to create an account for an ApsaraDB RDS for PostgreSQL instance and grant permissions to this account, see Create an account and Create a database.

    Database Password

    The password that is used to access the database.

    Encryption

    Specifies whether to encrypt the connection to the source database. You can configure this parameter based on your business requirements. In this example, Non-encrypted is selected.

    If you want to establish an SSL-encrypted connection to the source database, perform the following steps: Select SSL-encrypted, upload CA Certificate, Client Certificate, and Private Key of Client Certificate as needed, and then specify Private Key Password of Client Certificate.

    Note
    • If you set Encryption to SSL-encrypted for a self-managed PostgreSQL database, you must upload CA Certificate.

    • If you want to use the client certificate, you must upload Client Certificate and Private Key of Client Certificate and specify Private Key Password of Client Certificate.

    • For information about how to configure SSL encryption for an ApsaraDB RDS for PostgreSQL instance, see SSL encryption.

  6. Click Test Connectivity and Proceed in the lower part of the page.

    Note
    • Make sure that the CIDR blocks of DTS servers can be automatically or manually added to the security settings of the source and destination databases to allow access from DTS servers. For more information, see Add the CIDR blocks of DTS servers.

    • If the source or destination database is a self-managed database and its Access Method is not set to Alibaba Cloud Instance, click Test Connectivity in the CIDR Blocks of DTS Servers dialog box.

  7. Configure the objects to be synchronized.

    1. In the Configure Objects step, configure the objects that you want to synchronize.

      Parameter

      Description

      Parameter

      Description

      Synchronization Types

      The synchronization types. By default, Incremental Data Synchronization is selected. You must also select Schema Synchronization and Full Data Synchronization. After the precheck is complete, DTS synchronizes the historical data of the selected objects from the source database to the destination cluster. The historical data is the basis for subsequent incremental synchronization.

      Note

      If you select Schema Synchronization, DTS synchronizes the schemas of the tables to be synchronized from the source database to the destination database. The schemas include foreign keys.

      Processing Mode of Conflicting Tables

      • Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have identical table names, the precheck is passed. Otherwise, an error is returned during the precheck, and the data synchronization task cannot be started.

        Note

        If the source and destination databases contain tables with identical names and the tables in the destination database cannot be deleted or renamed, you can use the object name mapping feature to rename the tables that are synchronized to the destination database. For more information, see Map object names.

      • Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases.

        Warning

        If you select Ignore Errors and Proceed, data inconsistency may occur and your business may be exposed to potential risks.

        • If the source and destination databases have the same schema and a data record in the destination database has the same primary key value or unique key value as a data record in the source database:

          • During full data synchronization, DTS does not synchronize the data record to the destination database. The existing data record in the destination database is retained.

          • During incremental data synchronization, DTS synchronizes the data record to the destination database. The existing data record in the destination database is overwritten.

        • If the source and destination databases have different schemas, data may fail to be initialized. In this case, only some columns are synchronized, or the data synchronization task fails. Proceed with caution.

      Synchronization Topology

      The synchronization topology of the data synchronization task. Select Two-way Synchronization.

      Enable Exactly-Once Write

      Specifies whether to enable the Exactly-Once write feature. If the objects to be synchronized include tables that do not have primary keys and UNIQUE constraints, select Yes. For more information, see Synchronize tables without primary keys or UNIQUE constraints.

      Exclude DDL Operations

      • Yes: excludes DDL operations.

      • No: synchronizes DDL operations.

      Important

      DDL operations can be synchronized only in the forward direction from the source database to the destination database. DDL operations are ignored in the reverse direction from the destination database to the source database. Therefore, this parameter is displayed only when you configure the task in the forward direction.

      Conflict Resolution Policy

      If you encounter the conflicts described in the Conflict detection section of this topic, select a conflict resolution policy based on your business requirements.

      • TaskFailed

        If a conflict occurs during data synchronization, the data synchronization task reports an error and exits the process. The task enters a failed state, and you must manually resolve the conflict.

      • Ignore

        If a conflict occurs during data synchronization, the data synchronization task ignores the current statement and continues the process. The conflicting records in the destination database are used.

      • Overwrite

        If a conflict occurs during data synchronization, the conflicting records in the destination database are overwritten.

      Note

      If a latency occurs when you pause or restart a data synchronization task, the selected conflict resolution policy does not take effect during the latency. By default, data in the destination database is overwritten by the data that is synchronized during the latency.

      Capitalization of Object Names in Destination Instance

      The capitalization of database names, table names, and column names in the destination instance. By default, DTS default policy is selected. You can select other options to ensure that the capitalization of object names is consistent with that in the source or destination database. For more information, see Specify the capitalization of object names in the destination instance.

      Source Objects

      Select one or more objects from the Source Objects section and click the 向右 icon to add the objects to the Selected Objects section.

      Note

      You can select columns, tables, or schemas as objects to be synchronized.

      Selected Objects

      • To rename an object that you want to synchronize to the destination instance, right-click the object in the Selected Objects section. For more information, see the "Map the name of a single object" section of the Map object names topic.

      • To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see the "Map multiple object names at a time" section of the Map object names topic.

      Note
      • To select the SQL operations performed on a specific database or table, right-click an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to synchronize.

      • To specify WHERE conditions to filter data, right-click a table in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information, see Use SQL conditions to filter data.

      • If you use the object name mapping feature to rename an object, other objects that are dependent on the object may fail to be synchronized.

    2. Click Next: Advanced Settings to configure advanced settings.

      Parameter

      Description

      Parameter

      Description

      Dedicated Cluster for Task Scheduling

      By default, DTS schedules the task to the shared cluster if you do not specify a dedicated cluster. If you want to improve the stability of data synchronization tasks, purchase a dedicated cluster. For more information, see What is a DTS dedicated cluster.

      Retry Time for Failed Connections

      The retry time range for failed connections. If the source or destination database fails to be connected after the data synchronization task is started, DTS immediately retries a connection within the time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set this parameter to a value greater than 30. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.

      Note
      • If you specify different retry time ranges for multiple data synchronization tasks that have the same source or destination database, the shortest retry time range takes precedence.

      • When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.

      Retry Time for Other Issues

      The retry time range for other issues. For example, if the DDL or DML operations fail to be performed after the data synchronization task is started, DTS immediately retries the operations within the time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set this parameter to a value greater than 10. If the failed operations are successfully performed within the specified time range, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.

      Important

      The value of the Retry Time for Other Issues parameter must be smaller than the value of the Retry Time for Failed Connections parameter.

      Enable Throttling for Full Data Migration

      During full data synchronization, DTS uses the read and write resources of the source and destination databases. This may increase the load on the database servers. You can configure the Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) parameters for full data synchronization tasks to reduce the load on the destination database server.

      Note

      This parameter is displayed only if Full Data Synchronization is selected for the Synchronization Types parameter.

      Enable Throttling for Incremental Data Synchronization

      Specifies whether to enable throttling for incremental data synchronization. You can enable throttling for incremental data synchronization based on your business requirements. To configure throttling, you must configure the RPS of Incremental Data Synchronization and Data synchronization speed for incremental synchronization (MB/s) parameters. This reduces the load on the destination database server.

      Environment Tag

      The environment tag that is used to identify the DTS instance. You can select an environment tag based on your business requirements. In this example, no environment tag is selected.

      Monitoring and Alerting

      Specifies whether to configure alerting for the data synchronization task. If the task fails or the synchronization latency exceeds the specified threshold, alert contacts will receive notifications. Valid values:

    3. Click Next Step: Data Verification to configure data verification.

      For more information about how to use the data verification feature, see Configure a data verification task.

  8. Save the task settings and run a precheck.

    • To view the parameters to be specified when you call the relevant API operation to configure the DTS task, move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters.

    • If you do not need to view or have viewed the parameters, click Next: Save Task Settings and Precheck in the lower part of the page.

    Note
    • Before you can start the data synchronization task, DTS performs a precheck. You can start the data synchronization task only after the task passes the precheck.

    • If the data synchronization task fails the precheck, click View Details next to each failed item. After you analyze the causes based on the check results, troubleshoot the issues. Then, rerun the precheck.

    • If an alert is triggered for an item during the precheck:

      • If an alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issue. Then, run a precheck again.

      • If an alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur, and your business may be exposed to potential risks.

  9. Wait until the success rate becomes 100%. Then, click Back.

  10. Configure a data synchronization task in the reverse direction.

    1. Wait until initial synchronization is complete and the data synchronization task in the forward direction is in the Running state.

    2. Find the data synchronization task in the reverse direction and click Configure Task.

    3. Configure the data synchronization task in the reverse direction by performing the operations described from Step 5 to Step 9.

      Important
      • When you configure the data synchronization task in the reverse direction, you must select the correct source and destination instances. The source instance in the reverse direction is the destination instance in the forward direction. The destination instance in the reverse direction is the source instance in the forward direction. You must also make sure that the parameter settings such as the database name, account, and password are consistent.

      • When you configure the source and destination databases of the data synchronization task in the reverse direction, the Instance Region parameter cannot be modified. The number of parameters that you need to configure for a data synchronization task in the reverse direction is less than that for a data synchronization task in the forward direction. Configure the parameters that are displayed in the console.

      • When DTS checks for conflicting tables in the reverse direction, the tables that have been synchronized to the destination instance in the forward direction are ignored in the Processing Mode of Conflicting Tables.

      • You cannot select the Selected Objects of the data synchronization task in the forward direction for the data synchronization task in the reverse direction.

      • We recommend that you do not use the object name mapping feature when you configure the data synchronization task in the reverse direction. Otherwise, data inconsistency may occur.

  11. After the data synchronization task in the reverse direction is configured, wait until both tasks enter the Running state. Two-way data synchronization is configured.

  • On this page (1)
  • Prerequisites
  • Limits
  • Billing
  • Supported synchronization topologies
  • Conflict detection
  • Supported objects to be synchronized
  • SQL operations that can be synchronized
  • Procedure
Feedback
phone Contact Us

Chat now with Alibaba Cloud Customer Service to assist you in finding the right products and services to meet your needs.

alicare alicarealicarealicare