Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

DOCSP-44974-v1.7-backport (478) #479

Merged
merged 1 commit into from
Nov 12, 2024
Merged

DOCSP-44974-v1.7-backport (478) #479

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions source/index.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,18 +8,16 @@ Cluster-to-Cluster Sync
.. default-domain:: mongodb

{+c2c-product-name+} provides continuous data synchronization or a
one-time data migration between two MongoDB clusters. You can enable
{+c2c-product-name+} with the :ref:`mongosync <c2c-mongosync>` utility.
one-time data migration between two MongoDB clusters. For notes and caveats on
continuous sync, see the :ref:`<mongosync-considerations>` page. You can
enable {+c2c-product-name+} with the :ref:`mongosync <c2c-mongosync>` utility.

``mongosync`` can continuously synchronize data between two clusters.
You can use ``mongosync`` to create dedicated analytics, development,
or testing clusters that mirror your production environment.
Synchronized clusters can also support locality requirements for audit
and data residency compliance.

In addition to continuous data synchronization, ``mongosync`` can also
facilitate a one time data migration between clusters.

For an overview of the ``mongosync`` process, see :ref:`about-mongosync`.

To get started with ``mongosync``, refer to the :ref:`Quick Start Guide
Expand Down