Question

A retail company is migrating a 4 TB self-managed MySQL database running on-premises to Amazon RDS for MySQL. The business requires near-zero downtime during cutover and needs assurance that all rows migrated correctly before the application is repointed. The initial full load has already completed successfully. Which approach best satisfies both the low-downtime and data-integrity requirements?

Accepted Answer

Enable AWS DMS change data capture (CDC) to continuously replicate ongoing changes after the full load, run DMS data validation to compare source and target rows, and cut over during a brief maintenance window once the replication lag is near zero.

Answer

Take a final mysqldump export from the source after stopping writes, restore it to RDS, and manually spot-check a sample of tables before repointing the application.

Answer

Use AWS DataSync to synchronize the underlying MySQL data directory files to the RDS instance and enable checksum verification to confirm integrity.

Answer

Create a read replica of the on-premises database in RDS using native MySQL binlog replication only, then promote it without additional validation to minimize downtime.