Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
19 changes: 15 additions & 4 deletions source/quickstart.txt
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@
Quickstart
==========


.. default-domain:: mongodb

.. contents:: On this page
Expand All @@ -25,15 +24,27 @@ the rest of the {+c2c-product-name+} documentation.
Setup
-----

{+c2c-product-name+} syncs data between two clusters. To run
``mongosync``, you will need to:
``mongosync`` syncs data between two clusters.

- Each cluster can be a replica set or a sharded cluster. If either
is a sharded cluster, consult the :ref:`sharded cluster limitations
<c2c-sharded-limitations>` for ``mongosync``.

- Sharded clusters are not required to have the same number of shards.

- The destination cluster must be the same version or up to two versions ahead
of the source cluster. The patch version is not important, so long as they
meets the minimum patch :ref:`version requirements
<c2c-server-version-compatibility>`.

To run ``mongosync``, you need to:

#. Define a source and a destination cluster.
#. Define administrative users.
#. Download and install ``mongosync``.
#. Connect the clusters.

Follow the instructions below to setup {+c2c-product-name+}.
Follow the instructions below to set up {+c2c-product-name+}.

.. procedure::
:style: normal
Expand Down
2 changes: 2 additions & 0 deletions source/reference/limitations.txt
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,8 @@ Unsupported Collection Types
- Clustered collections with :ref:`expireAfterSeconds
<db.createCollection.expireAfterSeconds>` set aren't supported.

.. _c2c-sharded-limitations:

Sharded Clusters
----------------

Expand Down