Cluster-to-Cluster Sync. Continuous data sync between separate MongoDB clusters.

Continuously synchronize data between MongoDB clusters in the same or hybrid environments, including Atlas, private cloud, on-premises, and at the edge.

MongoDB Cluster-to-Cluster Sync allows you to easily migrate data to the cloud, spin up dev/test environments, create dedicated analytics environments, and support audits & data residency requirements.

Expand innovation beyond the limits of a single cluster Support all your multi-environment clusters by synchronizing data in Atlas with on-premises and edge data. Build innovative use cases that take full advantage of cluster-to-cluster data synchronization. Simplify data migrations, improve development lifecycles, or spin off dedicated analytics environments.

Take full control of your data synchronization Start, stop, pause, and resume your cluster synchronization as needed. The synchronization process can be paused for hours or even days, depending on the size of your MongoDB oplog. This includes the ability to pick up where you left off in the event of a hardware failure or system error.

Enable data movement with reliability The only MongoDB solution for enabling long-running cross-cluster sync. Seamlessly sync real-time data across your clusters to create target read-only clusters.

Features

• **Hybrid environments: **Synchronize data between different deployment environments: Atlas, private cloud, on-premises, or edge.
• **Continuous synchronization: **Seamlessly access real-time data that is continuously synchronized across source and destination clusters.
• **Filtered Sync: **Synchronize specific data sets rather than the entire cluster.
• **Unlike Topology Support: **Sync between clusters with different sharding configurations including from a replica set to a sharded cluster.
• **High resiliency: **Synchronization is resilient to a replica set election on the source and destination clusters.
• **Resumability: **Pause and resume your data synchronization as needed. Restart from where you left off even in the event of network-connection failure.
• **Encrypted transfer: **Securely synchronize across clusters with end-to-end encryption.
• **Reverse direction: **Reverse the direction of synchronization, swapping source and destination clusters when necessary.