A company is migrating their on-premises MySQL database to Cloud SQL using Database Migration Service (DMS). The source database is MySQL 5.7, and the target is a Cloud SQL MySQL 8.0 instance. The migration job is set to continuous, but after the full dump phase, the CDC phase keeps failing with the error 'binary log not found'. What is the most likely cause?
Trap 1: Cloud SQL Auth Proxy is not configured on the source.
Cloud SQL Auth Proxy is for connecting to Cloud SQL, not for source MySQL.
Trap 2: The Cloud SQL instance does not have binary logging enabled.
Cloud SQL is the target; binary logging is not required on the target for DMS.
Trap 3: The DMS migration job uses the wrong source connection profile.
A wrong connection profile would cause failure earlier, not specifically a missing binlog error.
- A
Cloud SQL Auth Proxy is not configured on the source.
Why wrong: Cloud SQL Auth Proxy is for connecting to Cloud SQL, not for source MySQL.
- B
The Cloud SQL instance does not have binary logging enabled.
Why wrong: Cloud SQL is the target; binary logging is not required on the target for DMS.
- C
The DMS migration job uses the wrong source connection profile.
Why wrong: A wrong connection profile would cause failure earlier, not specifically a missing binlog error.
- D
The source MySQL binary logs have been purged before DMS could replicate them.
If source binary logs are purged (e.g., due to low retention), DMS cannot find them and CDC fails.