This topic describes how to migrate data from Amazon Aurora MySQL to Alibaba Cloud POLARDB for MySQL by using Alibaba Cloud Data Transmission Service (DTS).
- The source instance can be connected through the public network.
- An Amazon Aurora instance that supports MySQL 5.6 is created.
- An ApsaraDB for POLARDB cluster is created.
- An account with the read and write permissions is created.
- You can migrate data only from Amazon Aurora MySQL 5.6.
- Schema migration for events is not available.
- DTS reads floating-point values (including float values and double values) in a column of the MySQL database by using the round (column,precision) method. If the value precision is not specified, the precision is 38 for float values and 308 for double values. Therefore, you must check whether the migration precision meets your service expectations.
- If object name mapping is enabled for an object, other objects depending on this object may fail to be migrated.
- If incremental data migration is selected, binlogging must be enabled for the source MySQL instance.
- If incremental data migration is selected, the binlog_format parameter of the source database must be set to row.
- If incremental data migration is selected and the source MySQL version is 5.6, the binlog_row_image parameter must be set to full.
- If binlog file ID disorder occurs in the source MySQL instance because of cross-host migration or reconstruction during incremental data migration, the incremental data being migrated may be lost.
We recommend that you back up data before performing migration tasks.
DTS attempts to recover abnormal tasks executed within seven days. This may lead to data in the source database overwriting the service data that has been written to the destination database. Therefore, after a migration task is completed, you must run the
revokecommand to revoke the write permission of the DTS account that is used to access the destination instance.
- Log on to the Amazon Aurora instance. Click the name of the source database and view the endpoint and port of the database in the connection information.
- Log on to the DTS console.
- In the left-side navigation pane, click Data Migration. In the right pane, click Create Migration Task in the upper-right corner.
- (Optional) Set the task name.
DTS generates a name for each task automatically. The task name is not required to be unique. You can change the task name as needed. We recommend that you choose an informative name so that the task can be easily identified.
- Configure information about the source and destination databases. The following table
describes the parameters.
Database type Parameter Description Source Database Instance Type The type of the source instance. Select User-Created Database with Public IP Address. Instance Region The region where the source database resides. If you have configured access control for your instance, you need to allow the public IP address range of the specified region to access the instance before configuring a migration task.Note You can click Get IP Address Segment of DTS to view and copy the IP address range of the region. Database Type The source database type. Select MySQL. Hostname or IP Address The endpoint of the Amazon Aurora database. Port Number The port of the Amazon Aurora database. Database Account The account with the read and write permissions on the Amazon Aurora database. Database Password The password of the Amazon Aurora database account. Destination Database Instance Type The type of the destination instance. Select POLARDB. Instance Region The region where the destination instance resides. POLARDB Instance ID The ID of the destination instance in the selected region. Database Account The account with the read and write permissions on the destination instance. Database Password The password of the account for accessing the destination instance.
- Click Test Connectivity and verify that the test results for both the source and target databases are Passed.
- Click Set Whitelist and Next in the lower-right corner of the page.
- Select the migration type. In the Available section, select the objects to be migrated, and click to move the objects to the Selected section.
Note To maintain data consistency before and after migration, we recommend that you select Schema Migration, Full Data Migration, and Incremental Data Migration.
Currently, Schema Migration and Full Data Migration are free of charge, while Incremental Data Migration charges the users by hour based on link specifications.
- Click Precheck and wait until the precheck ends.
Note If the precheck fails, you can fix the problems as instructed and run the precheck again.
- Click Next. In the Confirm Settings dialog box that appears, read the Data Transmission Service (Pay-As-You-Go) Service Terms, select the checkbox to agree to them, and then click Buy and Start.
If you select Incremental Data Migration, DTS synchronizes the data changes in the source database to the destination ApsaraDB for POLARDB cluster during incremental data migration. The migration task does not stop automatically. If you only want to migrate data, we recommend that you stop data writing to the source database for a few minutes when there is no delay in incremental data migration. After the incremental data migration enters the no-delay status again, stop the migration task and switch the services to the destination ApsaraDB for POLARDB cluster.
- Select the destination region to view the migration status. The status will be Completed when the migration is completed.
Data is migrated from Amazon Aurora MySQL to POLARDB for MySQL.