This topic introduces the preparations required before using DTS for data synchronization to ensure smooth configuration and operation of the data synchronization task.

Applicable scenarios	Network used for data migration	Preparations to be executed
The source database or target database is located in the IDC and plans to connect via the public network.	Public network	Add the IP address of the DTS server to the allowlist of the self-managed database.
The source or target database is deployed locally but does not have a public IP address.	Public network (via other servers)	The following preparations are required: Connect the local or third-party cloud database to the database gateway. Add the IP address range of the DTS server to the allowlist of the self-managed database.

tip

You can view and copy the CIDR block by clicking View DTS IP segment in the Source database information area on the Configuring source and target database page.

You can also prepare the migration objects in the source and target databases according to the instructions in the Pre-check items. For details, refer to Pre-check items.

When the instance type is RDS for MySQL and the access method is MySQL connected over public network (such as the source database being an instance of a third-party cloud service), you need to retain logs (e.g., Binlog) for at least 24 hours. Retaining logs for more than 7 days is recommended. Otherwise, the DTS task may fail because it can not obtain logs, potentially causing the task to fail and sometimes resulting in inconsistent or lost data.

Last updated: 2026.01.21 17:33:35

Public security network record in Beijing: No. 11010802032137