tencent cloud

Feedback

Migration from MongoDB to TencentDB for MongoDB

Last updated: 2021-12-23 16:08:35

    This document describes how to use the data migration feature of DTS to migrate data from MongoDB to TencentDB for MongoDB.

    MongoDB supports heterogeneous migration between replica set and sharded cluster, i.e., four source-target architecture scenarios: replica set-replica set, replica set-sharded cluster, sharded cluster-replica set, sharded cluster-sharded cluster.

    Notes

    • During full data migration, DTS consumes certain source database resources, which may increase the load and pressure of the source database. If your database configuration is low, we recommend you migrate the data during off-peak hours.
    • To migrate instances over the public network, make sure that the source instance is accessible from the public network.

    Prerequisites

    • You have created a TencentDB for MongoDB instance.
    • The source and target databases must meet the requirements for the migration feature and version as instructed in Databases Supported by Data Migration.
    • You have completed all preparations.
    • You need to create a read-only account in the source database for the migration; otherwise, the precheck will fail.
      use admin
      db.createUser({
       user: "username",
       pwd: "password",
       roles:
           [
               {role: "readAnyDatabase", db: "admin"},
               {role: "read", db: "local"}
           ]
      })
      

    Restrictions

    • To ensure migration efficiency, cross-region migration of CVM-based self-built instances is not supported.
    • Incremental migration is not supported for self-built single-node instances as they have no oplogs.

    Operation Restrictions

    • During migration, do not perform the following operations; otherwise, the migration task will fail:
      • Do not modify or delete user information (including username, password, and permissions) in the source and target databases and port numbers.
      • Do not clear oplogs in the source database.
      • Do not delete the target database TencetDTSData during data migration.
      • Manipulate data in the target database with caution during data migration; otherwise, data inconsistency may occur.
      • As DTS will filter out the DDL operations of the sharded cluster, do not perform DDL operations other than transactions on the source database during shard migration; otherwise, data inconsistency may occur.
    • If you only perform full data migration, do not write new data into the source database during migration; otherwise, the data in the source and target databases will be inconsistent. In scenarios with data writes, to ensure the data consistency in real time, we recommend you select full + incremental data migration.

    Supported SQL Operations

    Note:

    Only replica set migration supports DDL operations, while shard migration will filter out DDL operations (except transactions).

    Operation Type Supported SQL Operation
    DML INSERT, UPDATE, and DELETE
    DDL INDEX: createIndexes, createIndex, dropIndex, and dropIndexes
    COLLECTION: createCollection, drop, collMod, renameCollection, and convertToCapped
    DATABASE: dropDatabase and copyDatabase

    Environment Requirements

    Type Environment Requirements
    Source database requirements
  • The server where the source database resides must have enough outbound bandwidth; otherwise, the migration speed will be affected.
  • The user account provided by the source database must have permission to read the database.
  • The source database cannot have a database named TencetDTSData.
  • If the source database is in cluster mode, the balancer must be disabled before incremental sync.
  • Oplogs must be obtained from the source database during full + incremental migration.
  • Target database requirements
  • The space of the target database must be at least 1.3 times the size of the tables to be migrated in the source database.
  • The user account provided by the target database must have the root privilege.
  • The target database cannot have a database named TencetDTSData.
  • The target database cannot have tables with the same name as those in the source database.
  • If the source database is a shard, you must enter the correct mongos, config server, and mongod node information.
  • The target database cannot have active businesses; otherwise, a warning will be reported.
  • The shardkey information of the source and target databases must be the same; otherwise, a warning will be reported.
  • Migration Directions

    1. Log in to the DTS console, select Data Migration on the left sidebar, and click Create Migration Task to enter the Create Migration Task page.
    2. On the Create Migration Task page, select the region of the target database and click Free Trial. Currently, the DTS data migration feature is free of charge.
    3. On the Set source and target databases page, configure the task, source database, and target database settings.
      Note:

      Create a read-only account in the source database for migration; otherwise, the precheck will fail.

      Setting TypeConfiguration ItemDescription
      Task Configuration Task Name Set a meaningful name for easy task identification.
      Running Mode
      • Immediate execution: the task will be started immediately after the task verification is passed.
      • Scheduled execution: you need to configure a task execution time and the task will be started automatically then.
      Tag Tags are used to manage resources by category in different dimensions. If the existing tags do not meet your requirements, go to the console to create more.
      Source Database Settings Source Database TypeSelect your source database type. In this document, select **MongoDB**.
      Access TypeSelect a type based on your scenario. In this document, select **Database**.
      • Public Network: the source database can be accessed through a public IP.
      • Self-Build on CVM: the source database is deployed in a CVM instance.
      • Direct Connect: the source database can be interconnected with VPCs through Direct Connect.
      • VPN Access: the source database can be interconnected with VPCs through VPN Connection.
      • Database: the source database is a TencentDB database.
      • CCN: the source database can be interconnected with VPCs through CCN.
      For a third-party cloud database, you can select **Public Network** generally or select **VPC Access**, **Direct Connect**, or **CCN** based on your actual network conditions. For the preparations for different access types, see Overview.
      RegionSelect the region of the source MongoDB database.
      Database InstanceSelect the instance ID of the target database.
      AccountAccount of the source MongoDB database, which must have the required permissions.
      PasswordPassword of the source MongoDB database.
      Target Database Settings Target Database TypeSelect **MongoDB**.
      Access TypeIn this document, select **Database**.
      RegionSelect the same region as in the source database settings.
      Database InstanceSelect the instance ID of the target database.
      Account.Account of the target database, which must have the required permissions.
      PasswordPassword of the target database.
    4. Test the connectivity between the source and target databases.
    5. On the Set migration options and select migration objects page, set the migration options and migration objects (you can select specified databases and tables).
      Configuration ItemDescription
      Migration Type Select a type based on your scenario.
      • Structural migration: structured data such as databases and tables in the database will be migrated.
      • Full migration:the entire database will be migrated.
      • Full + incremental migration: the entire database and subsequent incremental data will be migrated. If there are data writes during migration, and you want to smoothly migrate the data in a non-stop manner, select this option.
      Migration Object
      • Entire instance: migrate the entire database instance, including the metadata definitions of roles and users but excluding system databases such as system objects in PostgreSQL.
      • Specified objects: migrate specified objects.
      Specify object Select the objects to be migrated in **Source Database Object** and move them to the **Selected Object** box.
    6. On the Verify task page, complete the precheck and click Start Task.
      If the verification failed, fix the problem as instructed in Fix for Verification Failure and initiate the verification task again.
      • Failed: it indicates that a check item failed and the task is blocked. You need to fix the problem and run the verification task again.
      • Alarm: it indicates that a check item doesn't completely meet the requirements, and the task can be continued, but the business will be affected. You need to assess whether to ignore the alarm or fix the problem and continue the task based on the alarm message.
    7. Return to the migration task list. After the incremental sync is 100% complete, click Complete in the Operation column to complete the migration task.
      • Select Structural migration or Full migration: once completed, the task will be stopped automatically.
      • Select Full + Incremental migration: after full migration is completed, the migration task will automatically enter the incremental data sync stage, which will not stop automatically. You need to click Complete to manually stop the incremental data sync.
      • Select an appropriate time to manually complete the incremental data sync and perform business switch.
        • You can see that the migration task is in the incremental sync stage, and there is no latency. Stop writing the source database for several minutes.
        • When the source-target database data gap is 0 MB, and the source-target database time lag is 0s, manually complete the incremental sync.
    8. (Optional) If you want to view, delete, or perform other operations on a task, click the task and select the target operation in the Operation column. For more information, see Task Management.
    9. After the migration task status becomes Task successful, you can formally cut over the business. For more information, see Cutover Description.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support