This topic describes how to migrate the data of a standalone instance or a replica set instance across regions by using Data Transmission Service (DTS). DTS supports both full data migration and incremental data migration. You can use these two methods together to migrate the data of an ApsaraDB for MongoDB instance across regions without interruptions to your business.

Prerequisites

Background information

You may need to migrate the data of an ApsaraDB for MongoDB instance across regions in the following situations:

  • You want to restructure your business.
  • You want to use the ApsaraDB for MongoDB instance to provide database services for applications deployed on an ECS instance, but the two instances are in different regions.

In the following example, an ApsaraDB for MongoDB instance in the China (Qingdao) region is migrated to an instance in the China (Hangzhou) region.

Migrate MongoDB instances to other regions
Note The procedure described in this topic shows how to migrate the data of only the source instance. If you no longer need the source instance after the migration is complete, you can release the instance.

Precautions

  • DTS uses resources of the source and destination instances during full data migration. This may increase the load of the database server. If the data volume is large or the specification is low, the database server may become unavailable. We recommend that you migrate your data during off-peak hours to avoid business interruptions.
  • To ensure data consistency, we recommend that you do not write data to the source instance when full data migration of a standalone instance is in progress.
  • If the source and destination instances run different database versions or storage engines, make sure that the instances do not have compatibility issues between them before you start the migration. For more information about the database versions and storage engines supported by ApsaraDB for MongoDB, see MongoDB versions and storage engines.

Billing

Migration type Instance configuration Internet traffic
Full data migration Free of charge. Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see DTS pricing.
Incremental data migration Charged. For more information, see DTS pricing.

Migration types

Migration type Description
Full data migration DTS migrates all historical data of the required objects from the source MongoDB database to the destination MongoDB database.
Note The following types of objects are supported: database, collection, and index.
Incremental data migration After full data migration is complete, DTS synchronizes incremental data from the source MongoDB database to the destination MongoDB database.
Note
  • The create and delete operations that are performed on databases, collections, and indexes can be synchronized.
  • The create, delete, and update operations that are performed on documents can be synchronized.

Required database account permissions

Data source Full data migration Incremental data migration
Source ApsaraDB for MongoDB instance Read permissions on the source database Read permissions on the source database, admin database, and local database
Destination ApsaraDB for MongoDB instance Read/write permissions on the destination database Read/write permissions on the destination database
Note For more information about how to create and authorize a database account, see Manage user permissions on MongoDB databases.

Procedure

  1. Log on to the DTS console.
  2. In the left-side navigation pane, click Data Migration.
  3. At the top of the Migration Tasks page, select the region where the destination ApsaraDB for MongoDB instance resides.
    Select a region
  4. In the upper-right corner of the page, click Create Migration Task.
  5. Configure both the source and destination databases.
    Configure the source and destination ApsaraDB for MongoDB databases
    Section Parameter Description
    N/A Task Name DTS automatically generates a task name. We recommend that you specify your own task name that helps identify the task. Task names do not need to be unique.
    Source Database Instance Type Select ApsaraDB for MongoDB.
    Instance Region Select the region where the source ApsaraDB for MongoDB instance resides. For this example, select China (Qingdao).
    MongoDB Instance ID Select the ID of the source ApsaraDB for MongoDB instance.
    Database Name Enter the name of the authentication database. It is the database where the database account is created.
    Note If the database account is root, enter admin.
    Database Account Enter the username of the database account that you use to manage the source database. For more information about the account permission requirements, see Required database account permissions.
    Database Password Enter the password of the database account.
    Note After you specify the source database information, click Test Connectivity next to Database Password to check whether the information is correct. If the information is correct, the Passed message is displayed. If the information is incorrect, the Failed message is displayed, and you must click Check next to the Failed message to modify the information.
    Destination Database Instance Type Select MongoDB Instance.
    Instance Region Select the region where the destination ApsaraDB for MongoDB instance resides. For this example, select China (Hangzhou).
    MongoDB Instance ID Select the ID of the destination ApsaraDB for MongoDB instance.
    Database Name Enter the name of the authentication database. It is the database where the database account is created.
    Note If the database account is root, enter admin.
    Database Account Enter the username of the database account that you use to manage the destination database. For more information about the account permission requirements, see Required database account permissions.
    Database Password Enter the password of the database account.
    Note After you specify the destination database information, click Test Connectivity next to Database Password to check whether the information is correct. If the information is correct, the Passed message is displayed. If the information is incorrect, the Failed message is displayed, and you must click Check next to the Failed message to modify the information.
  6. In the lower-right corner, click Set Whitelist and Next.
    Note DTS adds the CIDR blocks of DTS servers to the whitelists of the source and destination ApsaraDB for MongoDB instances. This ensures that DTS servers can connect to the source and destination ApsaraDB for MongoDB instances. After data migration is complete, you can remove the CIDR blocks of DTS servers from the whitelists. For more information, see Configure a whitelist for a sharded cluster instance.
  7. Configure migration types and migration objects.
    Select the migration types and objects to be migrated
    Parameter Description
    Migration Types
    • If you want to migrate all data, select Full Data Migration.
    • If you want to migrate data without interruptions to your business, select both Full Data Migration and Incremental Data Migration.
    Note
    • DTS does not support incremental data migration for standalone instances.
    • If Incremental Data Migration is not selected, do not write data into the source database during full data migration. This ensures data consistency between the source and destination databases.
    Available
    • In the Available section, select the objects you want to migrate and then click the icon to move them to the Selected section.
      Note Data in the admin and local databases cannot be migrated.
    • A migration object can be a database, collection, or function.
    • By default, the name of an object remains unchanged after migration. If you want a different object name after migration, use the object name mapping feature provided by DTS. For more information, see Object name mapping.
  8. In the lower-right corner of the page, click Precheck.
    Note
    • Before you can start the data migration task, a precheck is performed. You can start the data migration task only after the task passes the precheck.
    • If the task fails to pass the precheck, click the Info icon icon next to each failed item to view details. Troubleshoot the issues based on the causes and run the precheck again.
  9. After the task passes the precheck, click Next.
  10. In the Confirm Settings dialog box, specify the Channel Specification and select Data Transmission Service (Pay-As-You-Go) Service Terms.
  11. Click Buy and Start to start the migration task.
    • Full data migration

      We recommend that you do not manually stop a migration task. Otherwise, data migrated to the destination database will be incomplete. Wait until the migration task automatically stops.

    • Incremental data migration

      An incremental data migration task does not automatically stop. You must manually stop the migration task.

      Note Select an appropriate time to manually stop the migration task. For example, you can stop the migration task during off-peak hours or before you switch your workloads to the destination ApsaraDB for MongoDB instance.
      1. Wait until Incremental Data Migration and The migration task is not delayed appear in the progress bar of the migration task. Then, stop writing data to the source database for a few minutes. The delay time of incremental data migration may be displayed in the progress bar.
      2. After the status of incremental data migration changes to The migration task is not delayed, manually stop the migration task.Incremental data migration without delay

Subsequent operations

Determine whether to release the source instance.

  • If the source instance uses pay-as-you-go billing, release it. For more information, see Release an ApsaraDB for MongoDB instance.
  • If the source instance uses subscription billing, you cannot release it.