Skip to content

Commit ed326da

Browse files
DOCSP-44974-cluster-to-cluster-considerations-for-continuous-sync (#478)
* DOCSP-44974-cluster-to-cluster-considerations-for-continuous-sync * reviewer changes * rephrase * typo
1 parent 0592f38 commit ed326da

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

source/index.txt

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,16 @@ Cluster-to-Cluster Sync
77
.. default-domain:: mongodb
88

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

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

19-
In addition to continuous data synchronization, ``mongosync`` can also
20-
facilitate a one time data migration between clusters.
21-
2220
For an overview of the ``mongosync`` process, see :ref:`about-mongosync`.
2321

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

0 commit comments

Comments
 (0)