Trigger an Initial Sync for One Process¶

On this page

Considerations
Trigger Initial Sync

Use Cloud Manager Automation to start an initial sync process on one or more MongoDB instances. This resynchronizes data stored on MongoDB nodes in clusters.

Considerations¶

You can only resync secondary nodes.

A node might become the primary between the time when you trigger a resync and when it runs. In this case, the MongoDB Agent waits for you to connect to the node manually and run the rs.stepDown() command.
You can only schedule one node in any given replica set to resync at a given time. While one node resyncs, the Cloud Manager disables the :guilabel: Resync option for all other nodes.

Trigger Initial Sync¶

1

Navigate to the Clusters view for your deployment.¶

If it is not already displayed, select the organization that contains your desired project from the office icon Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
If it is not already displayed, click Deployment in the sidebar.
Click the Clusters view.

2

Choose a cluster with a node you want to resync.¶

Click the name of the deployment that contains the process to resync. Cloud Manager opens the deployment Overview.

3

Choose a node to resync.¶

Find the node that you want to resync.
Click the Actions dropdown for that node.

4

Click Resync.¶

5

Click Resync to confirm.¶

6

At the top of the deployment Overview, click Review & Deploy¶

7

Click Review & Deploy to review your changes.¶

Cloud Manager displays your proposed changes.

If you are satisfied, click Confirm & Deploy.
If you want to make further configuration changes, click Cancel.

Click Modify for the cluster to make additional changes.

Cloud Manager will no longer support Automation for MongoDB 3.4 clusters after February 10, 2022. Please upgrade your MongoDB deployment or migrate to Atlas.