Synchronize data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster - Data Transmission Service

This topic describes how to synchronize data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster by using Data Transmission Service (DTS).

Prerequisites

The source self-managed PostgreSQL database and the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster are created.
Note
- For more information about how to create a PolarDB for PostgreSQL (Compatible with Oracle) cluster, see Create a PolarDB for PostgreSQL (Compatible with Oracle) cluster.
- For more information about the supported database engine versions, see Overview of data synchronization scenarios.
The available storage space of the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster is larger than the total size of the data in the self-managed PostgreSQL database.

Usage notes

Note

During schema synchronization, DTS synchronizes foreign keys from the source database to the destination database.
During full data synchronization and incremental data synchronization, DTS temporarily disables the constraint check and cascade operations on foreign keys at the session level. If you perform the cascade update and delete operations on the source database during data synchronization, data inconsistency may occur.

Category	Description
Limits on the source database	The tables to be synchronized must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, the destination database may contain duplicate data records. Note If a destination table to receive data in a data synchronization task that you create not by using DTS (Schema Synchronization is not selected for the Synchronization Types parameter), make sure that the table and the table to be synchronized from the source database have the same PRIMARY KEY or NOT NULL UNIQUE constraints. Otherwise, the destination database may contain duplicate data records. 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. If you perform a primary/secondary switchover on the source self-managed PostgreSQL database, the data synchronization task fails. 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 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 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. 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 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	If you run a full or incremental data synchronization task, the tables to be synchronized from the source database contain foreign keys, triggers, or event triggers, and the account of the destination database is a privileged account, DTS temporarily sets the session_replication_role parameter to replica at the session level during full or incremental data synchronization. If the account of the destination database does not have the permission, you must manually set the session_replication_role parameter to replica in the destination database. During full or incremental data synchronization, if you perform cascade update or delete operations on the source database while the session_replication_role parameter is set to replica, 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 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, newly written sequences do not increment from the maximum value of the sequences in the source database. Therefore, before you switch your workloads to the destination database, you must update the starting value of the sequences in the destination database. 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 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 self-managed PostgreSQL database, you must log on to the secondary database to delete the replication 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 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.

Billing

Synchronization type	Task configuration fee
Schema synchronization and full data synchronization	Free of charge.
Incremental data 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.

SQL operations that can be synchronized

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 To use a data synchronization task created before May 12, 2023 to synchronize DDL operations, you must create triggers and functions in the source database to capture DDL information before you configure the data synchronization 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 database account of the self-managed PostgreSQL database must be a privileged account and the minor version of the database must be 20210228 or later. DTS supports the following DDL statements in data synchronization tasks: 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 self-managed PostgreSQL database must be PostgreSQL 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.

Permissions required for database accounts

Database	Required permission	References
Self-managed PostgreSQL database	Permissions of the superuser role	CREATE USER and GRANT (Transact-SQL)
PolarDB for PostgreSQL (Compatible with Oracle)	Permissions of the database owner	The database owner is specified when you create a database.

Preparations

Note

In this example, a self-managed PostgreSQL database that runs on a server of the Linux operating system is used.

Perform the following operations before you configure a data synchronization task:

Log on to the server on which the self-managed PostgreSQL database resides.

Modify the postgresql.conf configuration file. Set the wal_level parameter to logical, and make sure 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 in the self-managed PostgreSQL database and the number of DTS instances whose source database is the self-managed PostgreSQL database.

# - 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, restart the self-managed PostgreSQL database for the parameter settings to take effect.

Add the CIDR blocks of DTS servers to the pg_hba.conf configuration file of the self-managed PostgreSQL database. Add only the CIDR blocks of the DTS servers that reside in the same region as the destination database. For more information, see Add the CIDR blocks of DTS servers.
Note
- After you modify the configuration file, execute the SELECT pg_reload_conf(); statement or restart the self-managed PostgreSQL database for the modification to take effect.
- For more information about the pg_hba.conf configuration file, see The pg_hba.conf File. Skip this step if the IP address in the pg_hba.conf file is set to 0.0.0.0/0. The following figure shows the configurations.
Create the corresponding database and schema in the destination cluster based on the information of the database and schema of the object to be synchronized.

If the version of the self-managed PostgreSQL database is in the range of PostgreSQL 9.4.8 to PostgreSQL 10.0, you must perform the following operations before you configure a data synchronization task:

Download the PostgreSQL source code from the official website, compile the source code, and install PostgreSQL.
1. Log on to the server on which the self-managed PostgreSQL database resides.
2. Download the source code from the PostgreSQL official website based on the version of the self-managed PostgreSQL database.
3. Run the sudo ./configure, sudo make, and sudo make install commands in sequence to configure and compile the source code, and install PostgreSQL.
  Important
  When you compile and install PostgreSQL, the operating system version of PostgreSQL must be consistent with the GNU Compiler Collection (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 modify the command to sudo ./configure --without-readline.
  If you use another method to install PostgreSQL, you must compile ali_decoding in a test environment that has the same operating system version and GCC version.

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

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

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)

# Run the following commands to install the source code.
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, and run the sudo make and sudo make install commands in sequence to compile ali_decoding and obtain the files that are required to install ali_decoding.
Copy the files to the specified directories.

Create the corresponding database and schema in the destination cluster based on the information of the database and schema of the object to be synchronized.

Procedure

Go to the Data Synchronization Tasks page.
1. Log on to the Data Management (DMS) console.
2. In the top navigation bar, click Data + AI.
3. In the left-side navigation pane, choose DTS (DTS) > Data Synchronization.
Note
- 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.
- You can also go to the Data Synchronization Tasks page of the new DTS console.
On the right side of Data Synchronization Tasks, select the region in which the data synchronization instance resides.
Note
If you use the new DTS console, you must select the region in which the data synchronization instance resides in the top navigation bar.

Click Create Task. In the Create Data Synchronization Task wizard, configure the source and destination databases. The following table describes the parameters.

Category	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	Select a DMS database instance	The database that you want to use. You can choose whether to use an existing database based on your business requirements. If you select an existing database, DTS automatically populates the parameters for the database. If you do not select an existing database, you must configure the following database information.
	Database Type	The type of the source database. Select PostgreSQL.
	Access Method	The access method of the source database. Select Cloud Enterprise Network (CEN).
	Instance Region	The region where the self-managed PostgreSQL database resides.
	Replicate Data Across Alibaba Cloud Accounts	If data is synchronized within the same Alibaba Cloud account, select No.
	Connected VPC	The virtual private cloud (VPC) that is connected to the self-managed PostgreSQL database.
	IP Address	The server IP address of the self-managed PostgreSQL database.
	Port Number	The service port number of the self-managed PostgreSQL database. Default value: 5432.
	Database Name	The name of the self-managed PostgreSQL database.
	Database Account	The database account of the self-managed PostgreSQL database. For more information about the permissions that are required for the account, see Permissions required for database accounts.
	Database Password	The password that is used to access the database.
Destination Database	Select a DMS database instance	The database that you want to use. You can choose whether to use an existing database based on your business requirements. If you select an existing database, DTS automatically populates the parameters for the database. If you do not select an existing database, you must configure the following database information.
	Database Type	The type of the destination database. Select PolarDB (Compatible with Oracle).
	Access Method	The access method of the destination database. Select Express Connect, VPN Gateway, or Smart Access Gateway.
	Instance Region	The region in which the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster resides.
	Connected VPC	The VPC in which the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster is deployed.
	Domain Name or IP Address	The IP address of the primary node in the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. Note You can run the ping command on your computer to obtain the IP address that is used to access the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster.
	Port Number	The service port number of the destination database. Default value: 1521.
	Database Name	The name of the destination database in the PolarDB for PostgreSQL (Compatible with Oracle) cluster.
	Database Account	The database account of the destination PolarDB for PostgreSQL (Compatible with Oracle) cluster. For more information about the permissions that are required for the account, see Permissions required for database accounts.
	Database Password	The password that is used to access the database.

In the lower part of the page, click Test Connectivity and Proceed.
If the source or destination database is an Alibaba Cloud database instance, such as an ApsaraDB RDS for MySQL instance or an ApsaraDB for MongoDB instance, DTS automatically adds the CIDR blocks of DTS servers to the whitelist of the instance. If the source or destination database is a self-managed database hosted on an Elastic Compute Service (ECS) instance, DTS automatically adds the CIDR blocks of DTS servers to the security group rules of the ECS instance, and you must make sure that the ECS instance can access the database. If the database is deployed on multiple ECS instances, you must manually add the CIDR blocks of DTS servers to the security group rules of each ECS instance. If the source or destination database is a self-managed database that is deployed in a data center or provided by a third-party cloud service provider, you must manually add the CIDR blocks of DTS servers to the whitelist of the database to allow DTS to access the database. For more information, see the "CIDR blocks of DTS servers" section of the Add the CIDR blocks of DTS servers topic.
Warning
If the CIDR blocks of DTS servers are automatically or manually added to the whitelist of the database or instance, or to the ECS security group rules, security risks may arise. Therefore, before you use DTS to synchronize data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhancing the security of your username and password, limiting the ports that are exposed, authenticating API calls, regularly checking the whitelist or ECS security group rules and forbidding unauthorized CIDR blocks, or connecting the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.

Configure the objects to be synchronized and advanced settings.

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.
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.
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, perform the following steps: In the Selected Objects section, right-click an object. In the dialog box that appears, select the SQL operations that you want to synchronize. For more information about the SQL operations that can be synchronized, see SQL operations that can be synchronized. To specify WHERE conditions to filter data, right-click an object in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information about how to specify the conditions, see Specify filter conditions.

Click Next: Advanced Settings to configure advanced settings.

Parameter	Description
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: 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.
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.
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.

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.
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 instance. 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.