This topic describes how to migrate a self-managed standalone MongoDB database to an ApsaraDB for MongoDB instance by using Data Transmission Service (DTS).
You can also use the built-in commands of MongoDB to migrate self-managed MongoDB databases. For more information, see Migrate self-managed MongoDB databases to standalone instances by using tools provided by MongoDB.
For more information about data migration or synchronization solutions, see Overview.
Prerequisites
- The version of the self-managed MongoDB database is 3.0, 3.2, or 3.4.
- The available storage space of the ApsaraDB for MongoDB instance is larger than the total size of the data in the self-managed MongoDB database.
Precautions
- To prevent service disruptions, we recommend that you migrate data during off-peak hours.
- If the source and destination MongoDB databases use different versions or storage engines, make sure that your applications can run on both databases. For more information about the versions and storage engines that are supported by ApsaraDB for MongoDB, see MongoDB versions and storage engines.
- You cannot use DTS to migrate incremental data from a self-managed standalone MongoDB database because the oplog feature cannot be enabled for the database.
- The admin or local database cannot be used as the source or destination database.
Billing
| Migration type | Task configuration fee | Internet traffic fee |
|---|---|---|
| Full data migration | Free of charge. | Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see Pricing. |
Migration types
Full data migration: DTS migrates all historical data of the source MongoDB database to the destination MongoDB database.Note DTS can migrate the following types of objects: database, collection, and index.
Permissions required for database accounts
| Database | Full data migration |
|---|---|
| Self-managed MongoDB database | The read permissions on the source database |
| ApsaraDB for MongoDB instance | The read and write permissions on the destination database |
For more information about how to create and authorize a database account, see the following topics:
- Self-managed MongoDB database: db.createUser()
- ApsaraDB for MongoDB instance: Manage user permissions on MongoDB databases
Procedure
- Configure the source and destination databases.
Section Parameter Description N/A Task Name DTS automatically generates a task name. We recommend that you specify an informative name for easy identification. You do not need to use a unique task name. Source Database Instance Type Select an instance type based on the deployment of the source database. In this example, select User-Created Database with Public IP Address. Note If you select other instance types, you must deploy the network environment for the source database. For more information, see Preparation overview.Instance Region If you select User-Created Database with Public IP Address as the instance type, you do not need to specify the Instance Region parameter. Note If a whitelist is configured for the self-managed MongoDB database, you must add the CIDR blocks of DTS servers to the whitelist of the database. You can click Get IP Address Segment of DTS next to Instance Region to obtain the CIDR blocks of DTS servers.Database Type Select MongoDB. Hostname or IP Address Enter the endpoint that is used to connect to the self-managed MongoDB database. In this example, enter the public IP address. Port Number Enter the service port number of the self-managed MongoDB database. Note The service port of the self-managed MongoDB database must be accessible over the Internet.Database Name Enter the name of the authentication database. The database account is created in this database. Database Account Enter the account that is used to log on to the self-managed MongoDB database. For information about the permissions that are required for the account, see Permissions required for database accounts. Database Password Enter the password of the database account. Note After you specify the source database parameters, click Test Connectivity next to Database Password to verify whether the specified parameters are valid. If the specified parameters are valid, the Passed message appears. If the Failed message appears, click Check next to Failed. Modify the source database parameters based on the check results.Encryption Select Non-encrypted. Note You can select SSL-encrypted only when you migrate data from MongoDB Atlas.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. The database account is created in this database. Database Account Enter the database account of the destination ApsaraDB for MongoDB instance. For information about the permissions that are required for the account, see Permissions required for database accounts. Database Password Enter the password of the database account. Note After you specify the destination database parameters, click Test Connectivity next to Database Password to verify whether the specified parameters are valid. If the specified parameters are valid, the Passed message appears. If the Failed message appears, click Check next to Failed. Modify the destination database parameters based on the check results. - Select the migration types and the objects to be migrated.
Setting Description Select the migration types Select Full Data Migration because only full data migration is supported in this scenario. Note Incremental data migration is not supported in this scenario. To ensure data consistency, we recommend that you do not write data to the self-managed MongoDB database during full data migration.Select the objects to be migrated - Select one or more objects from the Available section and click the
icon to move the objects to the Selected section.
Note- DTS cannot migrate data from the admin or local database.
- The config database is an internal database. We recommend that you do not migrate data from the config database.
- You can select databases, collections, or functions as the objects to be migrated.
- By default, after an object is migrated to the destination database, the name of the object remains unchanged. You can use the object name mapping feature to rename the objects that are migrated to the destination database. For more information, see Object name mapping.
Specify whether to rename objects You can use the object name mapping feature to rename the objects that are migrated to the destination instance. For more information, see Object name mapping. Specify the retry time for failed connections to the source or destination database By default, if DTS fails to connect to the source or destination database, DTS retries within the next 12 hours. You can specify the retry time based on your needs. If DTS reconnects to the source and destination databases within the specified time, DTS resumes the data migration task. Otherwise, the data migration task fails. Note When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time based on your business needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released. - Select one or more objects from the Available section and click the
- 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, you can click the
icon next to each failed item to view details.
- You can troubleshoot the issues based on the causes and run a precheck again.
- If you do not need to troubleshoot the issues, you can ignore failed items and run a precheck again.