This topic was translated by AI and is currently in queue for revision by our editors. Alibaba Cloud does not guarantee the accuracy of AI-translated content. Request expedited revision
Home PageData Transmission ServiceUser GuideData Migration (New Console)Migrate data from a MySQL databaseMigrate self-managed MySQL to RDS MySQL
Search for Help Content

Migrate self-managed MySQL to RDS MySQL

Updated at: 2025-02-28 09:21
Community
important

This topic contains important information on necessary precautions. We recommend that you read this topic carefully before proceeding.

Data Transmission Service (DTS) enables the migration of MySQL databases from on-premises environments, ECS instances, or other cloud platforms to an RDS MySQL instance with minimal impact on business operations. DTS offers schema migration, full migration, and incremental migration, allowing for a seamless transition of a self-managed MySQL database to the cloud without interrupting the associated application.

Prerequisites

  • The self-managed MySQL database is now connected to Alibaba Cloud, and the IP address range of the DTS server has been included in the database's security settings, such as security group rules, firewall, or whitelist, to permit access. For more information, see Preparations.

    Note

    For a list of supported versions, see Migration Overview.

  • If you need to migrate incremental data, you must enable Binlog on your self-managed MySQL database. For more information, see how to create an account and configure Binlog for a self-managed MySQL database.

  • A target RDS MySQL instance with more storage space than that used by the self-managed MySQL database has been established. For details on instance creation, see Create an RDS MySQL instance.

Notes

Note

  • During schema migration, DTS transfers foreign keys from the source database to the destination database.

  • During full and incremental migrations, DTS temporarily suspends constraint checks and foreign key cascade operations at the session level. Should cascade updates or deletions occur in the source database while the task is running, this may lead to data inconsistencies.

Category

Description

Category

Description

Limits on the source database

  • The server on which the source database is deployed must have sufficient outbound bandwidth. Otherwise, the data migration speed decreases.

  • The tables to be migrated must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, the destination database may contain duplicate data records.

  • If you select tables as the objects to be migrated and you want to modify the tables in the destination database, such as renaming tables or columns, you can migrate up to 1,000 tables in a single data migration task. If you run a task to migrate more than 1,000 tables, a request error occurs. In this case, we recommend that you configure multiple tasks to migrate the tables or configure a task to migrate the entire database.

  • If you want to migrate incremental data, the following requirements for binary logs must be met:

    • The binary logging feature is enabled. The binlog_format parameter is set to row and the binlog_row_image parameter is set to full. Otherwise, error messages are returned during the precheck and the data migration task fails to be started.

      Important

      If the source database is a self-managed MySQL database deployed in a dual-primary cluster, you must set the log_slave_updates parameter to ON. This ensures that DTS can obtain all binary logs.

    • The binary logs of the source database must be stored for at least seven days. Otherwise, DTS may fail to obtain the binary logs and the task may fail. In exceptional circumstances, data inconsistency or loss may occur. Make sure that you configure the retention period of binary logs based on the preceding requirements. Otherwise, the service reliability or performance stated in the Service Level Agreement (SLA) of DTS may not be guaranteed.

  • Limits on operations to be performed on the source database:

    • During schema migration and full data migration, do not execute DDL statements to change the schemas of databases or tables. Otherwise, the data migration task fails.

    • If you perform only full data migration, do not write data to the source database during data migration. Otherwise, data inconsistency between the source and destination databases occurs. To ensure data consistency, we recommend that you select schema migration, full data migration, and incremental data migration as the migration types.

  • The data generated by change operation of binary logs, such as data restored from a physical backup or data from a cascade operation, is not recorded and migrated to the destination database when the data migration instance is running.

    Note

    If the change data is not recorded and migrated to the destination database, you can migrate full data again on the premise that your business is not affected.

  • If the source database is MySQL database 8.0.23 or later, and the data to be migrated includes invisible columns, the data of the columns cannot be obtained and data loss occurs.

    Note

    • To make the columns visible, run the ALTER TABLE <table_name> ALTER COLUMN <column_name> SET VISIBLE; command. For more information, see Invisible Columns.

    • Tables that do not have primary keys automatically generate invisible primary keys. You need to make the invisible primary keys visible. For more information, see Generated Invisible Primary Keys.

Other limits

  • To ensure compatibility, the versions of the source and destination MySQL databases must be the same.

  • DTS does not migrate data where a parser defined by using comments is used.

  • If the destination database is MySQL database 8.0.23 or later, and the columns to receive data include invisible columns, the destination columns to which the data is written cannot be found. In this case, the DTS instance fails to run and data loss occurs.

    Note

    • To make the columns visible, run the ALTER TABLE <table_name> ALTER COLUMN <column_name> SET VISIBLE; command. For more information, see Invisible Columns.

    • Tables that do not have primary keys automatically generate invisible primary keys. You need to make the invisible primary keys visible. For more information, see Generated Invisible Primary Keys.

  • If you do not use the schema migration feature of DTS in the data migration scenarios, you must ensure the compatibility of the fields. For example, if the field of a source table is of the text type, and the field of a destination table is of the varchar(255) type, the data may be truncated when the source table contains large fields.

  • If the data to be migrated contains information such as rare characters or emojis that takes up four bytes, the destination databases and tables to receive the data must use UTF8mb4 character set.

    Note

    If you use the schema migration feature of DTS, set the instance parameter character_set_server in the destination database to UTF8mb4 character set.

  • Before you migrate data, evaluate the impact of data migration on the performance of the source and destination databases. We recommend that you migrate data during off-peak hours. 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.

  • During full data migration, concurrent INSERT operations cause fragmentation in the tables of the destination database. After full data migration is complete, the tablespace of the destination database is larger than that of the source database.

  • You must make sure that the precision settings for columns of the FLOAT or DOUBLE data type meet your business requirements. DTS uses the ROUND(COLUMN,PRECISION) function to retrieve values from columns of the FLOAT or DOUBLE data type. If you do not specify a precision, DTS sets the precision for columns of the FLOAT data type to 38 digits and the precision for columns of the DOUBLE data type to 308 digits.

  • DTS attempts to resume data migration tasks that failed within the last seven days. Before you switch workloads to the destination database, you must stop or release the failed task. You can also execute the REVOKE statement to revoke the write permissions from the accounts that are used by DTS to access the destination database. Otherwise, the data in the source database overwrites the data in the destination database after a failed task is resumed.

  • If DDL statements fail to be executed in the destination database, the DTS task continues to run. You can view the DDL statements that fail to be executed in task logs. For more information about how to view task logs, see View task logs.

  • If you write column names that differ only in capitalization to the same table in the destination MySQL database, the data migration result may not meet your expectations because the column names in MySQL databases are not case-sensitive.

  • After data migration is complete, that is, the Status of the instance changes to Completed, we recommend that you run the analyze table <table name> command to check whether data is written to the destination table. For example, if a high-availability (HA) switchover is triggered in the destination MySQL database, data may be written only to the memory. As a result, data loss occurs.

  • If the source database is an ApsaraDB RDS for MySQL instance for which the EncDB feature is enabled, full data migration cannot be performed.

    Note

    ApsaraDB RDS for MySQL instances that have the Transparent Data Encryption (TDE) feature enabled support schema migration, full data migration, and incremental data migration.

  • If you want to migrate accounts from the source database to the destination database, you need to learn the prerequisites and precautions. For more information, see Migrate database accounts.

  • If a DTS task fails to run, DTS technical support will try to restore the task within 8 hours. During the restoration, the task may be restarted, and the parameters of the task may be modified.

    Note

    Only the parameters of the task may be modified. The parameters of databases are not modified. The parameters that may be modified include but are not limited to the parameters in the "Modify instance parameters" section of the Modify the parameters of a DTS instance topic.

Special cases

  • If the source database is a self-managed MySQL database, take note of the following limits:

    • If you perform a primary/secondary switchover on the source database when the data migration task is running, the task fails.

    • DTS calculates migration latency based on the timestamp of the latest migrated data in the destination database and the current timestamp in the source database. If no DML operation is performed on the source database for a long time, the migration latency may be inaccurate. If the latency of the data migration task is excessively high, you can perform a DML operation on the source database to update the latency.

      Note

      If you select an entire database as the object to be migrated, you can create a heartbeat table. The heartbeat table is updated or receives data every second.

    • DTS executes the CREATE DATABASE IF NOT EXISTS `test` statement in the source database as scheduled to move forward the binary log file position.

  • If the source database is an Apsara RDS for MySQL instance, take note of the following limit:

    • In incremental data migration, an ApsaraDB RDS for MySQL instance that does not record transaction logs, such as a read-only ApsaraDB RDS for MySQL V5.6 instance, cannot be used as the source database.

    • DTS executes the CREATE DATABASE IF NOT EXISTS `test` statement in the source database as scheduled to move forward the binary log file position.

  • If the destination database is an ApsaraDB RDS for MySQL instance, take note of the following limit:

    DTS automatically creates a database in the destination ApsaraDB RDS for MySQL instance. However, if the name of the source database does not comply with the database naming conventions of ApsaraDB RDS for MySQL, you must manually create a database in the destination ApsaraDB RDS for MySQL instance before you configure the data migration task. For more information, see Manage databases.

Pricing

Migration typeLink configuration feeData transfer cost
Migration typeLink configuration feeData transfer cost
Schema migration and full data migrationFree of charge.Data transfer fees are charged when data is migrated out of Alibaba Cloud over the Internet. For more information, see Billing overview.
Incremental data migrationCharged. For more information, see Billing overview.

Migration types

  • Schema migration

    Data Transmission Service (DTS) migrates the schemas of the selected objects from the source database to the destination database.

    Note

    • DTS supports schema migration for the following types of objects: tables, views, triggers, stored procedures, and stored functions.

      Note

      The routine_body of the stored procedure, routine_body of the stored functions, and select_statement of the views cannot be modified during the migration.

    • During schema migration, DTS changes the value of the SECURITY attribute from DEFINER to INVOKER for views, stored procedures, and functions. In addition, DTS sets the DEFINER to the destination database account used in the migration.

      Note

      The SECURITY attribute and DEFINER cannot be modified during the migration.

    • DTS does not migrate user information. To call a view, stored procedure, or stored function of the destination database, you must grant the read and write permissions to INVOKER.

  • Full data migration

    DTS migrates the historical data of required objects from the source database to the destination database.

  • Incremental data migration

    After full data migration is complete, DTS migrates incremental data from the source database to the destination database. Incremental data migration allows data to be migrated smoothly without interrupting the services of self-managed applications during data migration.

SQL operations that support incremental migration

Operation type

SQL statement

Operation type

SQL statement

DML

INSERT, UPDATE, and DELETE

DDL

  • ALTER TABLE and ALTER VIEW

  • CREATE FUNCTION, CREATE INDEX, CREATE PROCEDURE, CREATE TABLE, and CREATE VIEW

  • DROP INDEX and DROP TABLE

  • RENAME TABLE

    Important

    RENAME TABLE operations may cause data inconsistency between the source and destination databases. For example, if you select a table as the object to be migrated and rename the table during data migration, the data of this table is not migrated to the destination database. To prevent this situation, you can select the database to which this table belongs as the object to be migrated when you configure the data migration task. Make sure that the databases to which the table belongs before and after the RENAME TABLE operation are added to the objects to be migrated.

  • TRUNCATE TABLE

Permissions required for database accounts

Database

Schema migration

Full migration

Incremental migration

Database

Schema migration

Full migration

Incremental migration

Self-managed MySQL database

SELECT permission

SELECT permission

Incremental data migration: SELECT permission on the objects to migrate

REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW

The permissions to create databases and tables. The permissions allow DTS to create a database named dts to record heartbeat data during migration.

RDS MySQL instance

Access control list

For more information on creating and authorizing a database account, see the following topics:

Note

If you need to migrate the account information from the source database, the database account used to set up the task must have additional permissions. For more information, see Migrate database accounts.

Procedure

  1. Use one of the following methods to go to the Data Migration page and select the region in which the data migration instance resides.

    DTS console
    DMS console

    1. Log on to the DTS console.

    2. In the left-side navigation pane, click Data Migration.

    3. In the upper-left corner of the page, select the region in which the data migration instance resides.

    Note

    The actual operation may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.

    1. Log on to the DMS console.

    2. In the top navigation bar, move the pointer over Data Development > DTS (DTS) > Data Migration .

    3. From the drop-down list to the right of Data Migration Tasks, select the region in which the data synchronization instance resides.

  2. Click Create Task to go to the task configuration page.

  3. Optional. Click New Configuration Page in the upper-right corner of the page.

    Note

    • Skip this step if the Back to Previous Version button is displayed in the upper-right corner of the page.

    • Specific parameters in the new and previous versions of the configuration page may be different. We recommend that you use the new version of the configuration page.

  4. Configure the source and destination databases. The following table describes the parameters.

    Warning

    After you configure the source and destination databases, we recommend that you read the Limits that are displayed in the upper part of the page. Otherwise, the task may fail or data inconsistency may occur.

    Category

    Configuration

    Description

    Category

    Configuration

    Description

    None

    Task Name

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

    Source Database

    Select Existing Connection

    In this example, you do not need to configure this parameter. Configure the following database information.

    Database Type

    Select MySQL.

    Access Method

    Select a connection type based on the deployment location of the source database. In this topic, Public IP is used as an example to describe the configuration process.

    Note

    If a self-managed database is used as the source, you must perform the corresponding preparations. For more information, see Preparations overview.

    Instance Region

    Select the region where the source MySQL database resides.

    Domain Name or IP

    Enter the access address of the source MySQL database. In this example, enter the public address.

    Port

    Enter the service port of the source MySQL database (must be open to the Internet). The default value is 3306.

    Database Account

    Enter the account of the source MySQL database. For more information about the required permissions, see Permissions required for database accounts.

    Database Password

    The password that is used to access the database instance.

    Encryption

    Specifies whether to encrypt the connection to the source database. Select Non-encrypted or SSL-encrypted based on your business requirements.

    • If SSL encryption is not enabled for the self-managed MySQL database, select Non-encrypted.

    • If SSL encryption is enabled for the self-managed MySQL database, select SSL-encrypted. In this case, you must upload a CA Certificate and configure the CA Key parameter.

    Destination Database

    Select Existing Connection

    In this example, you do not need to configure this parameter. Configure the following database information.

    Database Type

    Select MySQL.

    Access Method

    Select Alibaba Cloud Instance.

    Instance Region

    Select the region where the destination RDS MySQL instance resides.

    Replicate Data Across Alibaba Cloud Accounts

    In this example, the migration is performed within the same Alibaba Cloud account. Select No.

    RDS Instance ID

    Select the ID of the destination RDS MySQL instance.

    Database Account

    Enter the database account of the destination RDS MySQL instance. For more information about the required permissions, see Permissions required for database accounts.

    Database Password

    The password that is used to access the database instance.

    Encryption

    Specifies whether to encrypt the connection to the source database instance. Select Non-encrypted or SSL-encrypted based on your business requirements. If you want to set this parameter to SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS for MySQL instance before you configure the DTS task. For more information, see Use a cloud certificate to enable SSL encryption.

  5. After completing the configuration, click Test Connectivity and Proceed at the bottom of the page. When the CIDR Blocks of DTS Servers dialog box appears, click Test Connectivity.

    Note

    Ensure that the DTS service's IP address range is added, either automatically or manually, to the security settings of both the source and destination databases to permit access by the DTS server. For more information, see how to add the IP address range of the DTS server.

  6. Configure the objects to be migrated.

    1. On the Configure Objects page, configure the objects that you want to migrate.

      Configuration

      Description

      Configuration

      Description

      Migration Types

      • 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 Schema Migration, make sure a database and a table are created in the destination database to receive data and the object name mapping feature is enabled in Selected Objects.

      • 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.

      Method to Migrate Triggers in Source Database

      Select a migration method for triggers that suits your specific needs. If the objects to be migrated do not include triggers, configuring this parameter is unnecessary. For more information, see how to configure trigger synchronization or migration.

      Note

      This parameter can be configured only if Migration Types, Schema Migration, and Incremental Data Migration are all selected.

      Enable Migration Assessment

      Evaluate whether the structures of the source and destination databases, such as index length, stored procedures, and dependent tables, meet the requirements. You can select Yes or No, based on your actual situation.

      Note

      • This parameter is configurable only when Migration Types is set to Schema Migration.

      • If you select Yes, the precheck duration may be extended. You can view the Assessment Result during the precheck. Note that the assessment result will not impact the outcome of the precheck.

      Processing Mode of Conflicting Tables

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

        Note

        If the source and destination databases contain tables with identical names and the tables in the destination database cannot be deleted or renamed, you can use the object name mapping feature to rename the tables that are migrated to the destination database. 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 the following potential risks:

        • If the source and destination databases have the same schema, and a data record has the same primary key as an existing data record in the destination database, the following scenarios may occur:

          • During full data migration, DTS does not migrate the data record to the destination database. The existing data record in the destination database is retained.

          • During incremental data migration, DTS migrates the data record to the destination database. The existing data record in the destination database is overwritten.

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

      Whether to migrate Event

      Select whether to migrate events from the source database based on your actual situation. If you select Yes, you must comply with the related requirements and perform subsequent operations. For more information, see Synchronize or migrate events.

      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 make sure that the capitalization of object names is consistent with that of 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 databases 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

      • Using the object name mapping feature may cause dependent objects to fail migration.

      • To set WHERE conditions for data filtering, right-click the table in Selected Objects and configure the filter conditions in the resulting dialog box. For details on configuring this parameter, see Set filter conditions.

      • To select specific SQL operations for migration at the database or table level, right-click the relevant object in Selected Objects and choose the SQL operations in the dialog box that appears. For more information on the supported operations, see SQL operations that support incremental migration.

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

      Configuration

      Description

      Configuration

      Description

      Dedicated Cluster for Task Scheduling

      By default, DTS schedules the data migration task to the shared cluster if you do not specify a dedicated cluster. If you want to improve the stability of data migration tasks, purchase a dedicated cluster. For more information, see What is a DTS dedicated cluster.

      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 data of 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, latency may occur for the data migration task.

      • 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 this option, 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 this option, the tables in the destination database may be locked.

      Whether to Migrate Accounts

      Choose whether to migrate the account information from the source database according to your specific needs. If you select Yes, you must also choose which accounts to migrate and verify their permissions.

      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 retry time range. Valid values: 10 to 1,440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS is reconnected to the source and destination databases within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails.

      Note

      • If you specify different retry time ranges for multiple data migration tasks that share the same source or destination database, the value that is specified later 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 the earliest opportunity after the source database and destination instance are released.

      Retry Time for Other Issues

      The retry time range for other issues. For example, if DDL or DML operations fail to be performed after the data migration task is started, DTS immediately retries the operations within the retry 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 retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails.

      Important

      The value of the Retry Time for Other Issues parameter must be smaller than the value of the Retry Time for Failed Connections parameter.

      Enable Throttling for Full Data Migration

      Specifies whether to 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 of the database servers. You can enable throttling for full data migration based on your business requirements. To configure throttling, you must 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 reduces the loads of the destination database server.

      Note

      You can configure this parameter only if you select Full Data Migration for the Migration Types parameter.

      Enable Throttling for Incremental Data Migration

      Specifies whether to enable throttling for incremental data migration. To configure throttling, you must configure the RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) parameters. This reduces the loads of the destination database server.

      Note

      You can configure this parameter only if you select Incremental Data Migration for the Migration Types parameter.

      Environment Tag

      Select an environment tag to identify the instance as needed. This parameter is not required in this example.

      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. Valid values:

      • 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, features such as physical backup and cloning of the source database may be affected.

      Configure ETL

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

      Monitoring and Alerting

      Specifies whether to configure alerting for the data migration task. If the task fails or the migration latency exceeds the specified threshold, the alert contacts receive notifications. Valid values:

    3. Click Next Step: Data Verification to configure the data verification task.

      For more information about how to use the data verification feature, see Configure a data verification task.

  7. Save the task settings and run a precheck.

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

    • If you do not need to view or have viewed the parameters, click Next: Save Task Settings and Precheck in the lower part of the page.

    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 analyze the causes based on the check results, troubleshoot the issues. Then, 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 the 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.

  8. Purchase an instance.

    1. Wait until Success Rate becomes 100%. Then, click Next: Purchase Instance.

    2. On the Purchase Instance page, configure the Instance Class parameter for the data migration instance. The following table describes the parameters.

      Section

      Parameter

      Description

      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 instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Instance classes of data migration instances.

    3. Read and agree to Data Transmission Service (Pay-as-you-go) Service Terms by selecting the check box.

    4. Click Purchase And Start . In the OK dialog box that appears, click OK .

      You can monitor the progress on the Data Migration page.

      Note

      If you need to switch your business, it is recommended to perform this operation during off-peak hours to ensure the migration instance experiences no latency or low latency. For more information, see Business Switching Process .

Previous: Migrate data from a MySQL databaseNext: Migrate data between ApsaraDB RDS for MySQL instances
  • On this page （1, M）
  • Prerequisites
  • Notes
  • Pricing
  • Migration types
  • SQL operations that support incremental migration
  • Permissions required for database accounts
  • Procedure
Feedback
phone Contact Us

Chat now with Alibaba Cloud Customer Service to assist you in finding the right products and services to meet your needs.

alicare alicarealicarealicare