Synchronize a self-managed PostgreSQL database to the cloud - Data Transmission Service

This topic describes how to use Data Transmission Service (DTS) to synchronize data from a self-managed PostgreSQL database to an ApsaraDB RDS for PostgreSQL instance.

Prerequisites

The source self-managed PostgreSQL database and the destination RDS for PostgreSQL instance must be created. For more information about how to create the destination RDS for PostgreSQL instance, see Create an RDS for PostgreSQL instance.
Note
- Note
  For more information about the supported versions of the source and destination databases, see Overview of data synchronization solutions.
- The version of the destination database is the same as or later than the version of the source database. This ensures database compatibility. If the version of the destination database is earlier than that of the source database, database compatibility issues may occur.
The available storage space of the destination ApsaraDB RDS for PostgreSQL instance must be larger than the storage space occupied by the source self-managed PostgreSQL database.

Precautions

Type	Description
Source database limits	The tables to be synchronized must have a primary key or a UNIQUE constraint, and the fields must be unique. Otherwise, duplicate data may appear in the destination database. Note If the target table is not created by DTS (the Synchronization Types is not set to Schema Synchronization), you must ensure that the table has the same primary key or non-null UNIQUE constraint as the corresponding table in the source database. Otherwise, duplicate data may appear in the target database. The name of the database to be synchronized cannot contain hyphens (-), such as dts-testdata. If you synchronize objects at the table level and need to edit them, such as mapping column names, and the number of tables in a single task exceeds 5,000, split the tables into multiple tasks. You can also configure a task to synchronize the entire database. Otherwise, a request error may be reported after you submit the task. DTS does not synchronize temporary tables, internal triggers, or some functions (C language functions and internal functions for PROCEDURE and FUNCTION) from the source database. DTS synchronizes some custom data (TYPE is COMPOSITE, ENUM, or RANGE) and the following constraints: primary key, foreign key, unique, and CHECK. WAL logs: Enable WAL logs. Set the wal_level parameter to logical. For an incremental synchronization task, DTS requires that WAL logs in the source database are retained for more than 24 hours. For a task that includes both full and incremental synchronization, DTS requires that WAL logs are retained for at least 7 days. You can change the log retention period to more than 24 hours after the full synchronization is complete. If the task fails because DTS cannot obtain the WAL logs, or in extreme cases, data becomes inconsistent or is lost because the log retention period is shorter than required, the issue is not covered by the DTS Service-Level Agreement (SLA). If a primary/secondary failover occurs in the self-managed PostgreSQL database, the synchronization fails. Make sure that the values of the max_wal_senders and max_replication_slots parameters are both greater than the sum of the number of replication slots currently in use and the number of DTS instances to be created with this self-managed PostgreSQL database as the source. If the source database has long-running transactions and the instance includes an incremental synchronization task, Write-Ahead Logging (WAL) logs before the long-running transactions are committed may not be cleared and can accumulate. This can cause insufficient disk space in the source database. When the source instance is Google Cloud Platform Cloud SQL for PostgreSQL, you must provide an account with `cloudsqlsuperuser` permissions for the Database Account of the source database. When you select objects to sync, you must select objects that this account has permission to manage, or grant the Owner permission for the objects to be synced to this account (for example, using the `GRANT <Owner of the object to be synced> TO <source database account used by the task>` command, you can enable this account to perform related operations as the owner of the object to be synced). Note An account with cloudsqlsuperuser permissions cannot manage data owned by another account with cloudsqlsuperuser permissions. Due to the limits of logical replication in the source database, if a single piece of data to be synchronized exceeds 256 MB after an incremental change, the synchronization instance may fail and cannot be recovered. You must reconfigure the synchronization instance. During initial schema synchronization and initial full data synchronization, do not perform Data Definition Language (DDL) operations that change the schema of databases or tables. Otherwise, the data synchronization task fails. Note During initial full data synchronization, DTS queries the source database. This creates metadata locks, which may block DDL operations on the source database. If you perform a major version upgrade on the source database while the synchronization instance is running, the instance fails and cannot be recovered. You must reconfigure the synchronization instance.
Other limits	A single data synchronization task can synchronize only one database. To synchronize multiple databases, configure a separate task for each database. Synchronization of TimescaleDB extension tables and tables with cross-schema inheritance is not supported. If a table to be synchronized contains fields of the SERIAL type, the source database automatically creates a Sequence for these fields. Therefore, when you configure Source Objects, if you set the Synchronization Types to Schema Synchronization, we recommend that you also select Sequence or synchronize the entire schema. Otherwise, the synchronization instance may fail. In the following three scenarios, you must run the `ALTER TABLE schema.table REPLICA IDENTITY FULL;` command on the tables to be synchronized before writing data to them. This ensures data consistency. During the execution of this command, do not perform table lock operations. Otherwise, the tables may be locked. If you skip the related check in the precheck, DTS automatically runs this command during the initialization of the instance. When the instance runs for the first time. When you select objects to synchronize at the schema level, and a new table is created in the schema or a table to be synchronized is rebuilt using the RENAME command. When you use the feature to modify synchronization objects. Note In the command, replace `schema` and `table` with the schema name and table name of the data to be synchronized. Perform this operation during off-peak hours. DTS validates data content but does not support the validation of metadata such as Sequences. You must validate metadata yourself. After you switch your business to the destination, new Sequences do not increment from the maximum value of the source Sequences. Before the switch, you must update the Sequence values in the destination database. For more information, see Update Sequence values in the destination database. DTS creates the following temporary tables in the source database to obtain information such as DDL statements for incremental data, the schema of incremental tables, and heartbeat data. Do not delete these temporary tables during synchronization. Otherwise, the DTS task may become abnormal. The temporary tables are automatically deleted after the DTS instance is released. `public.dts_pg_class`, `public.dts_pg_attribute`, `public.dts_pg_type`, `public.dts_pg_enum`, `public.dts_postgres_heartbeat`, `public.dts_ddl_command`, `public.dts_args_session`, and `public.aliyun_dts_instance`. To ensure the accuracy of the displayed synchronization latency, DTS adds a heartbeat table named dts_postgres_heartbeat to the source database. During data synchronization, DTS creates a replication slot with the prefix `dts_sync_` in the source database to replicate data. Using this replication slot, DTS can obtain incremental logs from the source database within the last 15 minutes. When the data synchronization fails or the instance is released, DTS attempts to clean up the replication slot. Note If you change the password of the source database account used by the task or delete the DTS IP address whitelist from the source database during synchronization, the replication slot cannot be automatically cleaned up. In this case, you must manually clean up the replication slot in the source database to prevent it from accumulating and occupying disk space, which can make the source database unavailable. If a primary/secondary failover occurs in the source database, you must log on to the secondary database to perform the cleanup. Before synchronizing data, evaluate the performance of the source and destination databases. Perform data synchronization during off-peak hours. Otherwise, initial full data synchronization consumes read and write resources on both the source and destination databases, which may increase the database load. Initial full data synchronization runs concurrent INSERT operations, which causes fragmentation in the destination database tables. As a result, the tablespace in the destination instance is larger than that in the source instance after the initialization is complete. For table-level data synchronization, if no data other than that from DTS is written to the destination database, you can use Data Management (DMS) to perform online DDL operations. For more information, see Change schemas without locking tables. During DTS synchronization, do not allow data from sources other than DTS to be written to the destination database. Otherwise, data inconsistency between the source and destination databases occurs. For example, if data from other sources is written to the destination database while you use DMS to perform online DDL operations, data may be lost in the destination database. If the task involves full or incremental synchronization and the tables to be synchronized in the source database 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 is a privileged account or has superuser permissions. If the destination database account does not have these permissions, you must manually set the session_replication_role parameter to replica in the destination database. During this period (when session_replication_role is replica), if cascade update or delete operations occur in the source database, data inconsistency may occur. After the DTS task is released, you can change the session_replication_role parameter back to origin. If an instance fails, DTS helpdesk will try to recover the instance within 8 hours. During the recovery process, operations such as restarting the instance or adjusting its parameters may be performed. Note When parameters are adjusted, only the parameters of the DTS instance are modified. The parameters in the database are not modified. The parameters that may be modified include but are not limited to those described in Modify instance parameters.

Billing description

Synchronization type	Task configuration fee
Schema synchronization and full data synchronization	Free of charge.
Incremental synchronization	Charged. For more information, see Billing overview.

Supported synchronization topologies

One-way one-to-one synchronization
One-way one-to-many synchronization
One-way cascade synchronization
One-way many-to-one synchronization

For more information about the synchronization topologies supported by DTS, see Synchronization topologies.

Supported synchronization objects

SCHEMA, TABLE.
Note
This includes PRIMARY KEY, UNIQUE KEY, FOREIGN KEY, DATATYPE (built-in data types), and DEFAULT CONSTRAINT.
VIEW, PROCEDURE (PostgreSQL 11 or later), FUNCTION, RULE, SEQUENCE, EXTENSION, TRIGGER, AGGREGATE, INDEX, OPERATOR, and DOMAIN.

SQL operations that can be synchronized

Operation type	SQL statement
DML	`INSERT`, `UPDATE`, `DELETE`
DDL	DDL operations can be synchronized only by data synchronization tasks that are created after . Important For data synchronization tasks created before May 12, 2023 (UTC+8), you must create triggers and functions in the source database to capture DDL information before you configure the task. For more information, see Use triggers and functions to implement incremental DDL migration for PostgreSQL databases. You cannot synchronize data of the `BIT` type during incremental data synchronization. The synchronization task supports the following DDL statements. The database account for the source database must be a privileged account, and the minor version of the self-managed PostgreSQL database must be 20210228 or later. `CREATE TABLE`, `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 PostgreSQL database must be PostgreSQL 11 or later.) `CREATE INDEX ON TABLE` Important You cannot synchronize additional information in DDL statements, such as `CASCADE` or `RESTRICT`. You cannot synchronize DDL statements from a session that runs the `SET session_replication_role = replica` command. You cannot synchronize DDL statements that are executed by calling a `FUNCTION`. If multiple SQL statements committed by the source database at the same time contain both DML and DDL statements, the DDL statements are not synchronized. 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. DDL statements executed directly within a plugin through the Server Programming Interface (SPI) are not supported.

Permissions required for database accounts

Database	Required permissions	How to create and grant permissions to an account
Self-managed PostgreSQL	superuser permission	Use the CREATE USER and GRANT syntax.
RDS for PostgreSQL	Owner permission on the SCHEMA	Create an account.

Preparations

Note

The following procedure uses a Linux operating system as an example.

Perform the following preparations for all versions of self-managed PostgreSQL databases.

Log on to the server where the self-managed PostgreSQL database resides.
Run the following command to query the number of used replication slots in the database.
```
select count(1) from pg_replication_slots;
```

Modify the postgresql.conf file. Set the wal_level parameter to logical. Ensure that the values of the max_wal_senders and max_replication_slots parameters are greater than the sum of the number of used replication slots and the number of DTS instances that use this self-managed PostgreSQL database as the source.

# - Settings -

wal_level = logical			# minimal, replica, or logical
					# (change requires restart)

......

# - Sending Server(s) -

# Set these on the master and on any standby that will send replication data.

max_wal_senders = 10		# max number of walsender processes
				# (change requires restart)
#wal_keep_segments = 0		# in logfile segments, 16MB each; 0 disables
#wal_sender_timeout = 60s	# in milliseconds; 0 disables

max_replication_slots = 10	# max number of replication slots
				# (change requires restart)

Note

After you modify the configuration file, you must restart the self-managed PostgreSQL database for the parameter settings to take effect.

Add the IP address of the DTS server to the pg_hba.conf file of the self-managed PostgreSQL database. You only need to add the DTS IP address CIDR block for the region where the destination database is located. For more information, see Add the CIDR blocks of DTS servers to the whitelist of a self-managed database.
Note
- After you modify the configuration file, run the SELECTpg_reload_conf(); command or restart the self-managed PostgreSQL database for the changes to take effect.
- For more information about the settings in this configuration file, see The pg_hba.conf File. If you have set the trusted address to 0.0.0.0/0 as shown in the following figure, you can skip this step.
Create the corresponding database and schema in the destination ApsaraDB RDS for PostgreSQL instance based on the database and schema information of the objects to be synchronized. The schema names must be the same. For more information, see Create a database and Manage schemas.

If your self-managed PostgreSQL database version is between 9.4.8 and 10.0, you must also perform the following preparations.

Download the PostgreSQL source code, and then compile and install it.
1. Log on to the server where the self-managed PostgreSQL database resides.
2. Download the source code that corresponds to the version of your source self-managed PostgreSQL database from the PostgreSQL official website.
3. Run the sudo ./configure, sudo make, and sudo make install commands in sequence to configure, compile, and install the source code.
  Important
  When you compile and install PostgreSQL, the operating system version must be compatible with the GCC version.
  If an error occurs when you run the sudo ./configure command, you can modify the command based on the error message. For example, if the error message is readline library not found. Use --without-readline to disable readline support., you can change the command to sudo ./configure --without-readline.
  If you choose another method to install PostgreSQL, you must compile ali_decoding in a staging environment that has the same operating system and GCC versions.

Download the ali_decoding extension provided by DTS, and then compile and install it.

Download ali_decoding.
Copy the entire ali_decoding directory to the contrib directory of the compiled and installed PostgreSQL.

Go to the ali_decoding directory and replace the content of the Makefile file with the following script:

# contrib/ali_decoding/Makefile
MODULE_big = ali_decoding
MODULES = ali_decoding
OBJS    = ali_decoding.o

DATA = ali_decoding--0.0.1.sql ali_decoding--unpackaged--0.0.1.sql

EXTENSION = ali_decoding

NAME = ali_decoding

#subdir = contrib/ali_decoding
#top_builddir = ../..
#include $(top_builddir)/src/Makefile.global
#include $(top_srcdir)/contrib/contrib-global.mk

#PG_CONFIG = /usr/pgsql-9.6/bin/pg_config
#pgsql_lib_dir := $(shell $(PG_CONFIG) --libdir)
#PGXS := $(shell $(PG_CONFIG) --pgxs)
#include $(PGXS)

# Use the following for source code installation
ifdef USE_PGXS
PG_CONFIG = pg_config
PGXS := $(shell $(PG_CONFIG) --pgxs)
include $(PGXS)
else
subdir = contrib/ali_decoding
top_builddir = ../..
include $(top_builddir)/src/Makefile.global
include $(top_srcdir)/contrib/contrib-global.mk
endif

Go to the ali_decoding directory. Run the sudo make and sudo make install commands in sequence to compile ali_decoding and obtain the files required for installation.
Copy the following files to the specified locations.

Based on the database and schema of the objects to sync, create a corresponding database and schema in the destination ApsaraDB RDS for PostgreSQL instance. The schema names must be the same. For more information, see Create a database and Manage schemas.

Procedure

Use one of the following methods to go to the Data Synchronization page and select the region in which the data synchronization instance resides.
DTS console
1. Log on to the DTS console.
2. In the left-side navigation pane, click Data Synchronization.
3. In the upper-left corner of the page, select the region in which the data synchronization task resides.
DMS console
Note
The actual operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.
1. Log on to the DMS console.
2. In the top navigation bar, move the pointer over Data + AI and choose DTS (DTS) > Data Synchronization.
3. From the drop-down list to the right of Data Synchronization Tasks, select the region in which the data synchronization instance resides.
Click Create Task to go to the task configuration page.

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.

Category	Configuration	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	Select PostgreSQL.
	Access Method	Select Cloud Enterprise Network (CEN).
	Instance Region	Select the region where the self-managed PostgreSQL database resides.
	CEN Instance ID	Select the ID of the CEN instance to which the self-managed PostgreSQL database belongs.
	Connected VPC	Select the VPC that is connected to the self-managed PostgreSQL database.
	Domain Name or IP	Enter the IP address of the server where the self-managed PostgreSQL database resides.
	Port Number	Enter the service port for the self-managed PostgreSQL database, which defaults to 3433.
	Database Name	Enter the name of the database in the self-managed PostgreSQL instance that contains the objects to be synchronized.
	Database Account	Enter the database account for the self-managed PostgreSQL database. For information about the required permissions, see Permissions required for database accounts.
	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	Select PostgreSQL.
	Access Method	Select Alibaba Cloud Instance.
	Instance Region	Select the region where the destination ApsaraDB RDS for PostgreSQL instance resides.
	Instance ID	Select the ID of the destination ApsaraDB RDS for PostgreSQL instance.
	Database Name	Enter the name of the database in the destination ApsaraDB RDS for PostgreSQL instance that will contain the synchronized objects.
	Database Account	Enter the database account for the destination ApsaraDB RDS for PostgreSQL instance. For information about the required permissions, see Permissions required for database accounts.
	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.

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 DTS server IP addresses to a whitelist.
- 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.

Configure the objects to be synchronized.

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

Configuration	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 instance fails. Proceed with caution.
Synchronization Topology	This is a one-way synchronization scenario. Select One-way Synchronization.
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 schemas or tables as the objects to be synchronized. If you select tables as the objects to be synchronized, DTS does not migrate other objects, such as views, triggers, and stored procedures, to the destination database. If a table to be synchronized contains SERIAL data type, and you select Schema Synchronization as the Synchronization Types, we recommend that you also select Sequence or entire schema synchronization.
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 which SQL operations to sync at the database or table level, right-click the object to be synchronized in the Selected Objects section. In the dialog box that appears, select the desired operations. To specify WHERE conditions to filter data, right-click a table in the Selected Objects section. In the dialog box that appears, specify the filter conditions. For more information, see Set filter conditions. If you use the object name mapping feature, other objects that depend on the mapped object may fail to synchronize.

Click Next: Advanced Settings to configure advanced settings.

Configuration	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 instances, 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 Synchronization	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 You can configure this parameter 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	You can select an environment tag to identify the instance.
Configure ETL	Specifies whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values: Yes: configures the ETL feature. You can enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: does not configure the ETL feature.
Monitoring and Alerting	Specifies whether to configure alerting for the data synchronization instance. If the task fails or the synchronization latency exceeds the specified threshold, alert contacts will receive notifications. Valid values: No: does not enable alerting. Yes: configures alerting. In this case, you must also configure the alert threshold and alert notification settings. For more information, see the "Configure monitoring and alerting when you create a DTS task" section of the Configure monitoring and alerting topic.

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.

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.

Purchase the instance.

Wait until the Success Rate becomes 100%. Then, click Next: Purchase Instance.

On the buy page, configure the Billing Method and Instance Class parameters for the data synchronization task. The following table describes the parameters.

Section	Parameter	Description
New Instance Class	Billing Method	Subscription: You pay for a subscription when you create a data synchronization instance. The subscription billing method is more cost-effective than the pay-as-you-go billing method for long-term use. Pay-as-you-go: A pay-as-you-go instance is billed on an hourly basis. The pay-as-you-go billing method is suitable for short-term use. If you no longer require a pay-as-you-go data synchronization instance, you can release the instance to reduce costs.
	Resource Group Settings	The resource group to which the data synchronization instance belongs. Default value: default resource group. For more information, see What is Resource Management?
	Instance Class	DTS provides instance classes that vary in synchronization speed. You can select an instance class based on your business requirements. For more information, see Instance classes of data synchronization instances.
	Subscription Duration	If you select the subscription billing method, specify the subscription duration and the number of data synchronization instances that you want to create. The subscription duration can be one to nine months, one year, two years, three years, or five years. Note This parameter is available only if you select the Subscription billing method.

Read and select Data Transmission Service (Pay-as-you-go) Service Terms.
Click Buy and Start. In the dialog box that appears, click OK.
You can view the progress of the task in the task list.