Migrating Yandex Managed Service for MongoDB clusters

To migrate your database to Managed Service for MongoDB, you need to directly transfer the data, acquire a write lock for the old database, and switch over the load to the database cluster in Yandex Cloud.

Performing migration with Data Transfer allows you to:

• Migrate the database without interrupting user service.
• Migrate from older MongoDB versions to newer versions.
• Go without creating an intermediate VM or granting online access to your Managed Service for MongoDB target cluster.

For more information, see What tasks Yandex Data Transfer is used for.

To use this migration method, allow connecting to the source cluster from the internet.

Getting startedGetting started

Create a Managed Service for MongoDB target cluster with the computing capacity and storage size appropriate for the environment where the migrated database is deployed.

The database name in the target cluster must be the same as the source database name.

Transferring dataTransferring data

1. Prepare the source cluster.

2. Prepare the target cluster.

3. Create a source endpoint with the following parameters:

   • Database type: MongoDB

   • Endpoint parameters → Connection settings: Custom installation

     Specify the parameters for connecting to the source cluster.

   Note

   The service does not support transferring Time Series collections, so you should exclude these collections in the endpoint settings.

4. Create a target endpoint with the following parameters:

   • Database type: MongoDB

   • Endpoint parameters → Connection settings: Managed Service for MongoDB cluster

     Specify the ID of the target cluster.

5. Create a transfer of the Snapshot and increment type that will use the created endpoints.

   To make large collections (over 1 GB) copy more quickly, enable parallel copy in the transfer settings. Specify two or more workers. The collection will split into the specified number of parts that will be copied concurrently.

   For parallel copy to work, the data type in the _id field should be the same for all documents in a collection. If a transfer discovers a type mismatch, the collection will not be partitioned but transferred in a single thread instead. If needed, remove documents with mismatched data types from the collection before starting a transfer.

   Note

   If a document with a different data type is added to a collection after a transfer starts, the transfer will move it at the replication stage after the parallel copy operation is completed. However, when re-enabled, the transfer will not be able to partition a collection because the _id field's type requirement will not be met for some of the documents in the collection.

6. Activate the transfer.

7. Wait for the transfer status to change to Replicating.

8. Switch the source cluster to read-only and transfer the load to the target cluster.

9. On the transfer monitoring page, wait for the Maximum data transfer delay metric to decrease to zero. This means that all changes that occurred in the source cluster after data copying was completed are transferred to the target cluster.

10. Deactivate the transfer and wait for its status to change to Stopped.

    For more information about transfer statuses, see Transfer lifecycle.

11. Delete the stopped transfer.

12. Delete endpoints for both the source and target.

See alsoSee also

For other migration methods, see the Yandex Managed Service for MongoDB documentation.