Skip to content

Commit eb2c4bf

Browse files
DOCSP-44974-cluster-to-cluster-considerations-for-continuous-sync (#478) (#479)
* DOCSP-44974-cluster-to-cluster-considerations-for-continuous-sync * reviewer changes * rephrase * typo
1 parent af6fbff commit eb2c4bf

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
@@ -8,18 +8,16 @@ Cluster-to-Cluster Sync
88
.. default-domain:: mongodb
99

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

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

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

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

0 commit comments

Comments
 (0)