Q: How do I handle a connection failure to the source database?
A: Check whether the source database information and settings are correct. For more information, see Source database connectivity check.
Q: How do I handle a connection failure to the destination database?
A: Check whether the destination database information and settings are correct. For more information, see Troubleshoot destination database connectivity failures.
Q: How do I perform data migration or data synchronization when the source or destination instance is in a region that DTS does not currently support?
For a data migration task, you can apply for a public endpoint for the database instance (for example, ApsaraDB RDS for MySQL) and connect it as Public IP Address. You can select a region that DTS supports as the instance region, and add the DTS server IP address ranges of the corresponding region to the whitelist of the instance. For the IP addresses to add to the whitelist, see Whitelist DTS server IP addresses.
For a data synchronization task, DTS does not currently support data synchronization in these regions because data synchronization does not support connecting a database instance as Public IP Address.
Q: If the source or destination instance is connected through a domain name, how long does it take DTS to detect the change?
A: DTS detects a domain name binding switchover within 10 minutes and automatically switches the DTS task to the new IP address bound to the domain name. Make sure that the binlog replication relationship between the old and new instances remains in place for more than 10 minutes during the domain name switchover.
Q: What do I do if the "Internal IP address instances are not allowed" error appears during a connection test?
Symptom: When the destination database is an AnalyticDB database, the connection test fails with the error "Internal IP address instances are not allowed" while you configure a migration or synchronization task.
Cause: The AnalyticDB destination database does not currently support connection tests.
Solution: When the destination database is an AnalyticDB database, you can skip the connection test and proceed with the subsequent configuration, provided that the username and password are correct.