From e15b8e76e00d97e0613040a286e6cf9ec3f1a0dd Mon Sep 17 00:00:00 2001 From: amalhotra-mdb <135728846+amalhotra-mdb@users.noreply.github.com> Date: Tue, 12 Nov 2024 13:48:59 -0500 Subject: [PATCH] DOCSP-44974-cluster-to-cluster-considerations-for-continuous-sync (#478) * DOCSP-44974-cluster-to-cluster-considerations-for-continuous-sync * reviewer changes * rephrase * typo --- source/index.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/source/index.txt b/source/index.txt index 85e44702b..af21bc88e 100644 --- a/source/index.txt +++ b/source/index.txt @@ -7,8 +7,9 @@ Cluster-to-Cluster Sync .. default-domain:: mongodb {+c2c-product-name+} provides continuous data synchronization or a -one-time data migration between MongoDB clusters. You can enable -{+c2c-product-name+} with the :ref:`mongosync ` utility. +one-time data migration between MongoDB clusters. For notes and caveats on +continuous sync, see the :ref:`` page. You can +enable {+c2c-product-name+} with the :ref:`mongosync ` utility. ``mongosync`` can continuously synchronize data between two clusters. You can use ``mongosync`` to create dedicated analytics, development, @@ -16,9 +17,6 @@ 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