Migrate data between ApsaraDB for MongoDB instances created by different Alibaba Cloud accounts

Prerequisites

• The source instance is either a standalone instance or a replica set instance. If the source instance is a sharded cluster instance, we recommend that you use the built-in commands of MongoDB to migrate data. For more information, see Migrate user-created MongoDB databases to Alibaba Cloud by using the built-in commands of MongoDB.
  Note You cannot use DTS to incrementally migrate the data of a standalone instance. For more information, see Migration types.
• The destination instance is created in the destination region. For more information, see Create a standalone ApsaraDB for MongoDB instance, Create a replica set instance, or Create a sharded cluster instance.
  Note The storage capacity of the destination instance must be greater than the occupied storage space of the source instance.

Precautions

• 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 while full data migration of a standalone instance is in progress.
• If the source and destination instances run different database versions or storage engines, ensure there are no compatibility issues between them before you start migration. For more information about the database versions and storage engines supported by ApsaraDB for MongoDB, see MongoDB versions and storage engines.

Billing

Migration types

Required database account permissions

Preparation

1. Log on to the ApsaraDB for MongoDB console with the Alibaba Cloud account to which the source instance belongs.
2. Apply for a public endpoint for the source instance. For more information, see Apply for a public endpoint for an ApsaraDB for MongoDB instance.
3. Add the Classless Inter-Domain Routing (CIDR) blocks of DTS servers to a whitelist of the source instance. For more information, see Configure a whitelist for an ApsaraDB for MongoDB instance.
   Note You can determine the CIDR blocks you need to add based on the region where the destination instance resides. For more information, see Add the CIDR blocks of DTS servers to the IP whitelist of on-premises databases. For example, if the source instance is in China (Hangzhou) and the destination instance is in China (Shenzhen), add the CIDR blocks of the DTS servers in China (Shenzhen) to a whitelist of the source instance.

Procedure

1. Log on to the DTS console with the Alibaba Cloud account to which the destination ApsaraDB for MongoDB instance belongs.
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.
   
4. In the upper-right corner of the page, click Create Migration Task.
5. Configure both the source and destination 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 User-Created Database with Public IP Address.
   	Instance Region	If you set the instance type to User-Created Database with Public IP Address, the system automatically specifies Instance Region.
   	Database Type	Select MongoDB.
   	Hostname or IP Address	Enter the domain name obtained from the public endpoint of the source instance. For example, enter dds-1udxxxxxxx-pub.mongodb.rds.aliyuncs.com.
   	Port Number	Enter 3717, which is the service port of the source 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 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 as prompted.
   Destination Database	Instance Type	Select MongoDB Instance.
   	Instance Region	Select the region where the destination ApsaraDB for MongoDB instance resides.
   	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 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 as prompted.

6. In the lower-right corner, click Set Whitelist and Next.
   Note The IP addresses of DTS servers are automatically added to a whitelist of the destination instance. This ensures that the DTS servers can connect to the destination instance. After the migration is complete, you can remove the IP addresses from the whitelist if you no longer need them. For more information, see Configure a whitelist.
7. Configure migration types and migration objects.
   

   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 You cannot use DTS to incrementally migrate the data of a standalone instance. 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 database cannot be migrated even if this database is selected. 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 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.

What to do next

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.

References

If you migrate data to a sharded cluster instance, you can configure data sharding as needed. For more information, see Configure sharding to maximize the performance of shards.