PoC environment
Migrate AWS RDS MySQL to Tidb Dedicated cloud
TiDB version: TiDB Cloud / TiDB 8.1
Hi All,
It seemed that using Dumpling + Lightning may help. However, how to replicate the incremental changes after the initial point-in-time load? using DM seems very slow and running for a long in initial load.
Any near zero download migration suggestion in this case?
Best Regards,
Andrew
To achieve near-zero downtime migration from AWS RDS MySQL to TiDB Dedicated Cloud for a database size greater than 5TB, you can follow these steps:
-
Initial Data Migration:
- Use tools like Dumpling and Lightning for the initial point-in-time load migration. Dumpling is used to dump the data from the source MySQL database, and Lightning is used to import the data into TiDB. This process helps in migrating the bulk of the data efficiently .
-
Replicating Incremental Changes:
- To replicate incremental changes after the initial data migration, you can consider using TiDB Data Migration (DM). While DM may seem slow during the initial load, it is a reliable tool for replicating incremental changes from the source database to the target TiDB database. By configuring DM appropriately, you can ensure that data changes are continuously synced from AWS RDS MySQL to TiDB Dedicated Cloud .
-
Near Zero Downtime Migration:
- To achieve near-zero downtime migration, you can implement a dual-write strategy where data is simultaneously written to both the AWS RDS MySQL and TiDB Dedicated Cloud databases. This ensures that both databases stay in sync during the migration process. Once you are confident that the data replication is working correctly, you can switch the application to read and write from TiDB Dedicated Cloud, thereby completing the migration with minimal downtime .
By following these steps and utilizing tools like Dumpling, Lightning, and TiDB Data Migration, you can perform a near-zero downtime migration from AWS RDS MySQL to TiDB Dedicated Cloud for a large database size.
Best Regards,
TiDB Assistant