Unlock the Power of AI

1 million free tokens

88% Price Reduction

Activate Now

Migrate data between ApsaraDB RDS instances of different Alibaba Cloud accounts

Updated at: 2025-03-04 10:11
important

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

You can migrate data between ApsaraDB RDS instances of different Alibaba Cloud accounts by using Data Transmission Service (DTS). This topic describes how to migrate data between ApsaraDB RDS instances of different Alibaba Cloud accounts.

Prerequisites

  • The IDs of the Alibaba Cloud accounts to which the source and destination ApsaraDB RDS instances belong are obtained. For more information about how to obtain the ID of an Alibaba Cloud account, see the Preparations section of this topic.

  • DTS is authorized by the Alibaba Cloud account to which the source ApsaraDB RDS instance belongs to access the resources of the account. A Resource Access Management (RAM) role is created, the required permissions are granted to the RAM role, and the trust policy is modified. For more information about how to grant permissions, see the Preparations section of this topic.

  • The destination ApsaraDB RDS instance is created. The available storage space of the destination ApsaraDB RDS instance is larger than the total size of the data in the source ApsaraDB RDS database.

    Note

    For more information about the supported versions of the source database and the destination instance, see Overview of data migration scenarios.

References

For more information about usage notes, see the following topics:

Billing rules

Migration type

Task configuration fee

Internet traffic fee

Migration type

Task configuration fee

Internet traffic fee

Schema migration and full data migration

Free of charge.

Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see Billing overview.

Incremental data migration

Charged. For more information, see Billing overview.

Permissions required for database accounts

Migrate data between ApsaraDB RDS for MySQL instances
Migrate data between ApsaraDB RDS for MySQL instances
Migrate data between ApsaraDB RDS for SQL Server instances
Migration between RDS SQL Server instances

Database type

Schema migration

Full data migration

Incremental data migration

The source ApsaraDB RDS for MySQL instance

The SELECT permission

The SELECT permission

Read and write permissions

Destination ApsaraDB RDS for MySQL instance

Read and write permissions

Read and write permissions

Read and write permissions

For more information about how to create an account for an ApsaraDB RDS for MySQL instance and grant permissions to the account, see Create an account on an ApsaraDB RDS for MySQL instance and Modify the permissions of a standard account on an ApsaraDB RDS for MySQL instance.

Note
  • If the source database account that you use is not created and granted permissions in the ApsaraDB RDS for MySQL console, make sure that the account has the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions.

  • If you want to migrate the account information of the source database, additional permissions are required for the source and destination database accounts that are used when you configure the DTS task. For more information, see Migrate database accounts.

Database

Schema migration

Full data migration

Incremental data migration

Source ApsaraDB RDS for MariaDB instance

The SELECT permission

The SELECT permission

The read and write permissions

Destination ApsaraDB RDS for MariaDB instance

The read and write permissions

The read and write permissions

The read and write permissions

For information about how to create a database account and grant permissions to the database account in an ApsaraDB RDS for MariaDB instance, see Create an account and Modify or reset account permissions.

Database type

Schema migration

Full data migration

Incremental data migration

Source ApsaraDB RDS for PostgreSQL instance

The USAGE permission on the pg_catalog schema

The SELECT permission on the objects to be migrated

Permissions of a privileged account that is the owner of the database

Note

If the source ApsaraDB RDS for PostgreSQL instance runs PostgreSQL 9.4 and you want to migrate only DML operations, only the REPLICATION permission is required for the database account.

Destination ApsaraDB RDS for PostgreSQL instance

The CREATE and USAGE permissions on the objects to be migrated

The permissions of the schema owner

For more information about how to create an account for an ApsaraDB RDS for PostgreSQL instance and grant permissions to the account, see Create an account and Create a database.

Database

Schema migration

Full migration

Incremental migration

Source RDS SQL Server instance

SELECT permission

SELECT permission

Permissions of the object owner

Destination RDS SQL Server instance

Access control list

Access control list

Access control list

For more information about how to create an account for an ApsaraDB RDS for SQL Server instance and grant permissions to the account, see Create a privileged account or a standard account and Modify the permissions of an account.

Procedure

Preparations

For more information about how to configure RAM authorization for the Alibaba Cloud account to which the database instance belongs, see Configure RAM authorization for cross-account DTS tasks.

Configure a task to migrate data between instances that belong to different Alibaba Cloud accounts

Note

The following example describes how to configure a task to migrate data between ApsaraDB RDS for MySQL instances that belong to different Alibaba Cloud accounts.

  1. Go to the Data Migration Tasks page by using the Alibaba Cloud account to which the destination ApsaraDB RDS instance belongs.

    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. Configure the source and destination databases. The following table describes the parameters.

    Section

    Parameter

    Description

    Section

    Parameter

    Description

    N/A

    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

    The instance that you want to use. You can choose whether to use 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 use an existing instance, you must configure the database information below.

    Note

    Database Type

    The type of the source database. Select MySQL.

    Access Method

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

    Instance Region

    The region in which the source ApsaraDB RDS instance resides.

    Note

    You can select different regions for the source and destination ApsaraDB RDS instances.

    Replicate Data Across Alibaba Cloud Accounts

    Specifies whether to migrate data across Alibaba Cloud accounts. In this example, Yes is selected.

    Alibaba Cloud Account

    The ID of the Alibaba Cloud account to which the source ApsaraDB RDS instance belongs.

    Note

    For more information, see the Obtain the ID of the Alibaba Cloud account to which the source database belongs section in the topic "Configure RAM authorization for cross-account DTS tasks".

    RAM Role Name

    The name of the RAM role that is configured for the Alibaba Cloud account to which the source ApsaraDB RDS instance belongs, for example, ram-for-dts.

    Note
    • Do not enter the AliyunDTSDefaultRole role that is the default role in DTS.

    • Do not enter the Alibaba Cloud Resource Name (ARN) of the RAM role.

    • For more information, see the Step 1: Create a RAM role section in the topic "Configure RAM authorization for cross-account DTS tasks".

    RDS Instance ID

    The ID of the source ApsaraDB RDS instance.

    Note

    If an alert message is displayed when you select an ApsaraDB RDS instance ID, modify the parameter settings as prompted. For more information about alert messages, see the Common errors section in the topic "Configure a DTS task across Alibaba Cloud accounts".

    Database Account

    The account of the source database. For more information about the required permissions for the account, see the Permissions required for database accounts section of this topic.

    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 requirements. In this example, Non-encrypted is selected.

    Note

    If you want to select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance before you configure the data migration task. For more information, see Configure the SSL encryption feature.

    Destination Database

    Select Existing Connection

    The instance that you want to use. You can choose whether to use 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 use an existing instance, you must configure the database information below.

    Note

    Database Type

    The type of the destination database. Select MySQL.

    Access Method

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

    Instance Region

    The region in which the destination ApsaraDB RDS instance resides.

    Note

    You can select different regions for the source and destination ApsaraDB RDS instances.

    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 ApsaraDB RDS instance.

    Database Account

    The account of the destination database. For more information about the permissions that are required for the account, see the Permissions required for database accounts section of this topic.

    Database Password

    The password that is used to access the database instance.

    Encryption

    Specifies whether to encrypt the connection to the destination database. Select Non-encrypted or SSL-encrypted based on your requirements. In this example, Non-encrypted is selected.

    Note

    If you want to select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance before you configure the data migration task. For more information, see Configure SSL encryption for an ApsaraDB RDS for MySQL instance.

  4. In the lower part of the page, click Test Connectivity and Proceed.

    Note
    • Make sure that the CIDR blocks of DTS servers can be automatically or manually added to the security settings of the source and destination databases to allow access from DTS servers. For more information, see Add the CIDR blocks of DTS servers.

    • If the source or destination database is a self-managed database and its Access Method is not set to Alibaba Cloud Instance, click Test Connectivity in the CIDR Blocks of DTS Servers dialog box.

  5. Configure the objects to be migrated.

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

      Parameter

      Description

      Parameter

      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

      The method that is 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

      This parameter is available only if you select Schema Migration and Incremental Data Migration for the Migration Types parameter.

      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 if you select Schema Migration when you configure the Migration Types parameter.

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

      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 向右小箭头 icon to 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 specify the name of an object to be migrated in the destination instance or specify the object to receive data in the destination instance, right-click the object in the Selected Objects section. For more information, see Map object names.

      • To remove one or more objects that are selected for migration, click the objects in the Selected Objects section and then click the image icon to move the objects to the Source Objects section.

      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 Specify filter conditions.

      • To select the SQL operations for incremental migration, right-click an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate.

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

      Parameter or setting

      Description

      Parameter or setting

      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

      Specifies whether to migrate accounts. In this example, No is selected.

      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.

      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.

      Environment Tag

      The environment tag that is used to identify the DTS instance. You can select an environment tag based on your business requirements. In this example, no environment tag is added.

      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.

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

  7. 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 Buy and Start. In the message that appears, click OK.

      You can view the progress of the task on the Data Migration page.

  • On this page (1)
  • Prerequisites
  • References
  • Billing rules
  • Permissions required for database accounts
  • Procedure
  • Preparations
  • Configure a task to migrate data between instances that belong to different Alibaba Cloud accounts
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