Migrating data from MySQL databases with homogeneous data migrations in Amazon DMS - Amazon Database Migration Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Migrating data from MySQL databases with homogeneous data migrations in Amazon DMS

You can use Homogeneous data migrations to migrate a self-managed MySQL database to RDS for MySQL or Aurora MySQL. Amazon DMS creates a serverless environment for your data migration. For different types of data migrations, Amazon DMS uses different native MySQL database tools.

For homogeneous data migrations of the Full load type, Amazon DMS uses mydumper to read data from your source database and store it on the disk attached to the serverless environment. After Amazon DMS reads all your source data, it uses myloader in the target database to restore your data.

For homogeneous data migrations of the Full load and change data capture (CDC) type, Amazon DMS uses mydumper to read data from your source database and store it on the disk attached to the serverless environment. After Amazon DMS reads all your source data, it uses myloader in the target database to restore your data. After Amazon DMS completes the full load, it sets up the binlog replication with the binlog position set to the start of the full load. To avoid data inconsistency, set the Number of jobs to 1 to capture consistent state of existing data. For more information, see Creating a data migration.

For homogeneous data migrations of the Change data capture (CDC) type, Amazon DMS requires the Native CDC start point to start the replication. If you provide the native CDC start point, then Amazon DMS captures changes from that point. Alternatively, choose Immediately in the data migration settings to automatically capture the start point for the replication when the actual data migration starts.

Note

For a CDC-only migration to work properly, all source database schemas and objects must already be present on the target database. The target may have objects that are not present on the source, however.

You can use the following code example to get the current log sequence number (LSN) in your MySQL database.

show master status

This query returns a binlog file name and the position. For the native start point, use a combination of the binlog file name and the position. For example, mysql-bin-changelog.000024:373. In this example, mysql-bin-changelog.000024 is the binlog file name and 373 is the position where Amazon DMS starts capturing changes.

The following diagram shows the process of using homogeneous data migrations in Amazon DMS to migrate a MySQL database to RDS for MySQL or Aurora MySQL.

An architecture diagram of the MySQL data migration with DMS Homogeneous Data Migrations.