All Products
Search
Document Center

ApsaraDB RDS:Migrate data from a Google Cloud SQL for MySQL instance to an ApsaraDB RDS for MySQL instance

Last Updated:Sep 28, 2023

This topic describes how to migrate data from a Google Cloud SQL for MySQL instance to an ApsaraDB RDS for MySQL instance. This topic also describes the usage notes.

Prerequisites

Source and destination

Requirement

References

Source

Google Cloud SQL for MySQL instance

  • The instance can be accessed over the Internet. The public endpoint and port of the instance are obtained.

  • A privileged account is created.

Google Cloud SQL for MySQL documentation

Destination

ApsaraDB RDS for MySQL instance

  • An RDS instance is created.

  • A privileged account is created.

Limits

  • The schema migration method does not support events.

  • Data Transmission Service (DTS) reads floating-point values of the FLOAT and DOUBLE data types in a column of the MySQL database by calling the round(column,precision) function. If the value precision is not specified, the precision is 38 bits for FLOAT-type values and 308 bits for DOUBLE-type values. You must check whether the precision of FLOAT-type values and DOUBLE-type values that are to be migrated by DTS meets your business requirements.

  • If you use the object name mapping feature on an object, other objects that are dependent on the object may fail to be migrated.

  • If incremental data migration is used, binary logging must be enabled for the Google Cloud SQL for MySQL instance.

  • If incremental data migration is used, the binlog_format parameter of the source database must be set to row.

  • If incremental data migration is used and the Google Cloud SQL for MySQL instance runs MySQL 5.6 or later, the binlog_row_image parameter of the instance must be set to full.

  • If incremental data migration is used and cross-host migration or reconstruction is performed on the Google Cloud SQL for MySQL instance during the incremental data migration, the IDs of binary log files may be disordered, and the incremental data that is migrated may be lost.

Note

For more information about how to modify the parameters of a Google Cloud SQL for MySQL instance, see Google Cloud SQL for MySQL documentation.

Usage notes

DTS attempts to automatically resume abnormal migration tasks that are run within seven days. Therefore, data on the Google Cloud SQL for MySQL instance may overwrite the service data that has been written to the ApsaraDB RDS for MySQL instance. After a migration task is complete, you must execute the REVOKE statement to revoke the write permissions of the DTS account that is used to access the ApsaraDB RDS for MySQL instance.

Procedure (in the new DTS console)

  1. Go to the Data Migration Tasks page.
    1. Log on to the Data Management (DMS) console.
    2. In the top navigation bar, click DTS.
    3. In the left-side navigation pane, choose DTS (DTS) > Data Migration.
    Note
  2. From the drop-down list next to Data Migration Tasks, select the region in which the data migration instance resides.
    Note If you use the new DTS console, you must select the region in which the data migration instance resides in the upper-left corner.
  3. Click Create Task. On the page that appears, configure the source and destination instances.

    Warning

    After you configure the source and destination databases, we recommend that you read the limits displayed at the top of the page. Otherwise, the task may fail or data inconsistency may occur.

    Section

    Parameter

    Description

    N/A

    Task Name

    The task name that DTS automatically generates. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to specify a unique task name.

    Source Database

    Select an existing DMS database instance

    The database instance that you want to use. You can choose whether to select an existing instance based on your business requirements.

    • If you select an existing instance, DTS automatically populates the parameters for the database.

    • If you do not select an existing instance, you must manually configure parameters for the database.

    Database Type

    The type of the source instance. Select MySQL.

    Access Method

    The access method of the source instance. Select Public IP Address.

    Instance Region

    The region of the source instance.

    Note

    If you cannot find the region in which the source instance resides, you can select a region that is closest to the instance.

    Hostname or IP Address

    The endpoint of the source instance.

    Note

    In the left-side navigation page of the Google Cloud SQL for MySQL DB instance, click Connections. In the Networking section of the SUMMARY tab, view the value of the Public IP address parameter.

    Port

    The port number of the source instance. The default port number is 3306.

    Database Account

    The database account of the source instance. For more information about account permissions, see Migrate data from an Amazon RDS for MySQL instance to an ApsaraDB RDS for MySQL instance

    Database Password

    The password of the database account.

    Destination Database

    Select an existing DMS database instance

    The database instance that you want to use. You can choose whether to select an existing instance based on your business requirements.

    • If you select an existing instance, DTS automatically populates the parameters for the database.

    • If you do not select an existing instance, you must manually configure parameters for the database.

    Database Type

    The type of the destination instance. Select MySQL.

    Access Method

    The access method of the destination database. Select Alibaba Cloud Instance.

    Instance Region

    The region of the destination instance.

    Replicate Data Across Alibaba Cloud Accounts

    Specifies whether data is migrated across Alibaba Cloud accounts. In this example, No is selected.

    RDS Instance ID

    The ID of the destination instance.

    Database Account

    The database account of the destination instance. For information about the account permissions, see Migrate data from an Amazon RDS for MySQL instance to an ApsaraDB RDS for MySQL instance.

    Database Password

    The password of the database account.

    Encryption

    Specifies whether to encrypt the connection to the source database. Select Non-encrypted or SSL-encrypted based on your business requirements. If you select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS for MySQL instance before you configure the data migration task. For more information, see Configure the SSL encryption feature.

  4. In the lower part of the page, click Test Connectivity and Proceed.
  5. If an IP address whitelist is configured for your self-managed database, you must add the CIDR blocks of DTS servers to the IP address whitelist. Then, click Test Connectivity and Proceed.

    Warning

    If the CIDR blocks of DTS servers are automatically or manually added to the IP address whitelist of the database instance or ECS security group rules, security risks may arise. Therefore, before you use DTS to migrate data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhance the security of your account and password, limit the ports that are exposed, authenticate API calls, regularly check the IP address whitelist or ECS security group rules and forbid unauthorized CIDR blocks, and connect the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.

  6. Configure the objects to be synchronized and advanced settings.

    Parameter

    Description

    Migration Type

    • To perform only full data migration, select Schema Migration and Full Data Migration.

    • To ensure service continuity during data migration, select Schema Migration, Full Data Migration, and Incremental Data Migration.

    Note

    If you do not select Incremental Data Migration, we recommend that you do not write data to the source database during data migration. This ensures data consistency between the source and destination databases.

    Processing Mode of Conflicting Tables

    • Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have the same names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started.

      Note

      You can use the object name mapping feature to rename the tables that are migrated to the destination database. You can use this feature if the source and destination databases contain tables that have identical names and the tables in the destination database cannot be deleted or renamed. For more information, see Map object names.

    • Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases.

      Warning

      If you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks.

      • If the source and destination databases have the same schema, DTS does not migrate data records that have the same primary keys as data records in the destination database.

      • If the source and destination databases have different schemas, only specific columns are migrated or the data migration task fails. Proceed with caution.

    • Precheck and Report Errors: checks whether the destination database contains collections that have the same names as collections in the source database. If the source and destination databases do not contain collections that have identical names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started.

      Note

      You can use the object name mapping feature to rename the collections that are migrated to the destination database. You can use this feature if the source and destination databases contain collections that have identical names and the collections in the destination database cannot be deleted or renamed. For more information, see Map object names.

    • Ignore Errors and Proceed: skips the precheck for identical collection names in the source and destination databases.

      Warning

      If you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks.

      • DTS does not migrate data records that have the same primary keys as data records in the destination database.

      • Data may fail to be initialized, only specific columns are migrated, or the data migration task fails.

    • Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have the same names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started.

    • Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases.

      Warning

      If you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks.

      • If the source and destination databases have the same schema, DTS does not migrate data records that have the same primary keys as data records in the destination database.

      • If the source and destination databases have different schemas, only specific columns are migrated or the data migration task fails. Proceed with caution.

    Method to Migrate Triggers in Source Database

    The method used to migrate triggers from the source database. You can select a migration method based on your business requirements. If no triggers are to be migrated, you do not need to configure this parameter. For more information, see Synchronize or migrate triggers from the source database.

    Note

    You can configure this parameter only when you select Schema Migration as a migration type.

    Enable Migration Assessment

    Specifies whether to enable migration assessment. Migration assessment aims to check whether the schemas of the source and destination databases, such as the length of indexes, stored procedures, and dependent tables, meet the requirements. You can select Yes or No based on your business requirements.

    Note
    • You can configure this parameter only when you select Schema Migration as a migration type.

    • If you select Yes, the precheck may take more time. You can view the Assessment Result during the precheck. The assessment results do not affect the precheck results.

    Capitalization of Object Names in Destination Instance

    The capitalization of database names, table names, and column names in the destination instance. By default, DTS default policy is selected. You can select other options to ensure that the capitalization of object names is consistent with that in the source or destination database. For more information, see Specify the capitalization of object names in the destination instance.

    Source Objects

    Select one or more objects from the Source Objects section. Click the Rightwards arrow icon and add the objects to the Selected Objects section.

    Note

    You can select columns, tables, or schemas as the objects to be migrated. If you select tables or columns as the objects to be migrated, DTS does not migrate other objects, such as views, triggers, or stored procedures, to the destination database.

    Selected Objects

    • To rename an object that you want to migrate to the destination instance, right-click the object in the Selected Objects section. For more information, see Map the name of a single object.
    • To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see Map multiple object names at a time.
    Note
    • If you use the object name mapping feature to rename an object, other objects that depend on the object may fail to be migrated.

    • To specify WHERE conditions to filter data, right-click a table in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information, see Use SQL conditions to filter data.

    • To migrate the SQL operations performed on a specific database or table, right-click the object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate.

  7. Click Next: Advanced Settings to configure advanced settings.

    • Data Verification Settings

      For more information about how to use the data verification feature, see Enable data verification.

    • Advanced Settings

      Parameter

      Description

      Select the dedicated cluster used to schedule the task

      By default, DTS schedules the task to a shared cluster. You do not need to configure this parameter. You can purchase a dedicated cluster of the specified specifications to run data migration tasks. For more information, see What is a DTS dedicated cluster?

      Set Alerts

      Specifies whether to set alerts for the data migration task. If the task fails or the migration latency exceeds the threshold, the alert contacts will receive notifications. Valid values:

      Copy the temporary table of the Online DDL tool that is generated in the source table to the destination database.

      If you use DMS or the gh-ost tool to perform online DDL operations on the source database, you can specify whether to migrate the temporary tables generated by online DDL operations. Valid values:

      Important

      You cannot use tools such as pt-online-schema-change to perform online DDL operations on the source database. Otherwise, the DTS task fails.

      • Yes: DTS migrates the data of temporary tables generated by online DDL operations.

        Note

        If online DDL operations generate a large amount of data, the data migration task may take an extended period of time to complete.

      • No, Adapt to DMS Online DDL: DTS does not migrate the data of temporary tables generated by online DDL operations. Only the original DDL operations that are performed by using DMS are migrated.

        Note

        If you select No, Adapt to DMS Online DDL, the tables in the destination database may be locked.

      • No, Adapt to gh-ost: DTS does not migrate the data of temporary tables generated by online DDL operations. Only the original DDL operations that are performed by using the gh-ost tool are migrated. You can use the default or custom regular expressions to filter out the shadow tables of the gh-ost tool and tables that are not required.

        Note

        If you select No, Adapt to gh-ost, the tables in the destination database may be locked.

      Retry Time for Failed Connections

      The retry time range for failed connections. If the source or destination database fails to be connected after the data migration task is started, DTS immediately retries a connection within the time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data migration task. Otherwise, the data migration task fails.
      Note
      • If you set different retry time ranges for multiple data migration tasks that have the same source or destination database, the shortest retry time range that is set takes precedence.
      • When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.

      The wait time before a retry when other issues occur in the source and destination databases.

      The retry time range for other issues. For example, if the DDL or DML operations fail to be performed after the data migration task is started, DTS immediately retries the operations within the time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set the parameter to a value greater than 10. If the failed operations are successfully performed within the specified time range, DTS resumes the data migration task. Otherwise, the data migration task fails.

      Important

      The value of the The wait time before a retry when other issues occur in the source and destination databases parameter must be smaller than the value of the Retry Time for Failed Connections parameter.

      Enable Throttling for Full Data Migration

      During full data migration, DTS uses the read and write resources of the source and destination databases. This may increase the loads on the database servers. You can enable throttling for full data migration based on your business requirements. To enable throttling, you need to configure the Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) parameters. This helps offload the destination instance.

      Note

      You can configure this parameter only when you select Full Data Migration as the migration type.Migration Types

      Enable Throttling for Incremental Data Migration

      You can enable throttling for incremental data migration based on your business requirements. To enable throttling, you need to configure the RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) parameters. This helps offload the destination instance.

      Note

      You can configure this parameter only when you select Incremental Data Migration as the migration type.Migration Types

      Environment Tag

      You can select environment tags based on your business requirements. In this example, you do not need to configure this parameter.

      Configure ETL

      Specifies whether to configure the extract, transform, and load (ETL) feature. For more information, see What is ETL?. Valid values:

      Whether to delete SQL operations on heartbeat tables of forward and reverse tasks

      Specifies whether to write SQL operations on heartbeat tables to the source database while the DTS instance is running.
      • Yes: does not write SQL operations on heartbeat tables. In this case, a latency of the DTS instance may be displayed.
      • No: writes SQL operations on heartbeat tables. In this case, specific features such as physical backup and cloning of the source database may be affected.
  8. In the lower part of the page, click Next: Save Task Settings and Precheck.

    You can move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters to view the parameters to be specified when you call the relevant API operation to configure the DTS task.

    Note
    • Before you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.

    • If the task fails to pass the precheck, click View Details next to each failed item. After you troubleshoot the issues based on the causes, run a precheck again.

    • If an alert is triggered for an item during the precheck:

      • If an alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.

      • If an alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur, and your business may be exposed to potential risks.

  9. Wait until the Success Rate value becomes 100%. Then, click Next: Purchase Instance.

  10. On the Purchase Instance page, specify the Instance Class parameter for the data migration instance. The following table describes the parameter.

    Section

    Parameter

    Description

    New Instance Class

    Resource Group

    The resource group to which the data migration instance belongs. Default value: default resource group. For more information, see What is Resource Management?.

    Instance Class

    DTS provides various instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Specifications of data migration instances.

  11. Read and select the check box to agree to Data Transmission Service (Pay-as-you-go) Service Terms.

  12. Click Buy and Start to start the data migration task. You can view the progress of the task in the task list.