|
1 | 1 | .. _c2c-index:
|
2 | 2 |
|
3 |
| -=============================== |
4 |
| -MongoDB Cluster-to-Cluster Sync |
5 |
| -=============================== |
| 3 | +======================= |
| 4 | +Cluster-to-Cluster Sync |
| 5 | +======================= |
6 | 6 |
|
7 | 7 | .. default-domain:: mongodb
|
8 | 8 |
|
9 |
| -The primary motivation of this initiative ... |
| 9 | +{+c2c-product-name+} provides you with continuous unidirectional |
| 10 | +data synchronization between two MongoDB clusters in the same or |
| 11 | +hybrid environments. Customers can enable {+c2c-product-name+} via |
| 12 | +the :ref:`c2c-mongosync` utility tool. |
10 | 13 |
|
11 |
| -NOTE: This page will have material that introduces C2C to the reader. |
| 14 | +``mongosync`` can continuously synchronize data between two clusters. |
| 15 | +You can use ``mongosync`` to create dedicated analytics, development, |
| 16 | +or testing clusters that mirror your production environment. |
| 17 | +Synchronized clusters can also support location requirements for audit |
| 18 | +and data residency compliance. |
| 19 | + |
| 20 | +In addition to continuous data synchronization, ``mongosync`` can also |
| 21 | +facilitate a one time data migration between clusters. |
| 22 | + |
| 23 | +To get started with ``mongosync``, refer to the :ref:`Quick Start Guide |
| 24 | +<c2c-quickstart>`. For more detailed information, refer to the |
| 25 | +:ref:`c2c-install` or :ref:`c2c-connecting` page that best fits your |
| 26 | +situation. |
| 27 | + |
| 28 | +To learn more about ``mongosync`` use cases, see: |
| 29 | + |
| 30 | +- :ref:`Continuous synchronization <c2c-uses-continue-sync>` |
| 31 | +- :ref:`Data migration <c2c-uses-migration>` |
| 32 | + |
| 33 | +The :ref:`Frequently Asked Questions (FAQ) <c2c-faq>` page addresses |
| 34 | +common questions users have asked about ``mongosync``. |
12 | 35 |
|
13 | 36 | .. toctree::
|
14 | 37 | :titlesonly:
|
|
0 commit comments