|
1 |
| -.. place holder for the reference section TOC |
2 |
| - |
3 | 1 | =========
|
4 | 2 | Reference
|
5 | 3 | =========
|
6 | 4 |
|
| 5 | +:ref:`c2c-mongosync` |
| 6 | + The primary process used in {+c2c-product-name+}. |
| 7 | + |
| 8 | +:ref:`c2c-config` |
| 9 | + Configure :program:`mongosync` instances at startup using a |
| 10 | + configuration file. |
| 11 | + |
| 12 | +:ref:`c2c-api` |
| 13 | + API endpoints to interact with ``mongosync``. |
| 14 | + |
| 15 | +:ref:`c2c-states` |
| 16 | + States that ``mongosync`` enters depending on requests received. |
| 17 | + |
| 18 | +:ref:`c2c-filtered-sync` |
| 19 | + Inclusion and exclusion filters to specify which databases and |
| 20 | + collections to include in sync. |
| 21 | + |
| 22 | +:ref:`c2c-oplog-sizing` |
| 23 | + Increase the size of the oplog on the source cluster for large data |
| 24 | + sets. |
| 25 | + |
| 26 | +:ref:`c2c-failure-recovery` |
| 27 | + Prepare for disaster recovery using :ref:`connections |
| 28 | + <c2c-connecting>` between clusters. |
| 29 | + |
| 30 | +:ref:`c2c-limitations` |
| 31 | + Limitations of ``mongosync``. |
| 32 | + |
| 33 | +:ref:`c2c-logging` |
| 34 | + A running log of events, including entries such as the copying |
| 35 | + collections and indexes, change stream events, and API calls. |
| 36 | + |
| 37 | +:ref:`c2c-permissions-and-roles` |
| 38 | + Required permissions on the source and destination clusters for the |
| 39 | + user specified in the ``mongosync`` connection string. |
| 40 | + |
| 41 | +:ref:`c2c-telemetry` |
| 42 | + Anonymous, aggregated usage data to improve MongoDB products. |
| 43 | + |
| 44 | +:ref:`c2c-verification` |
| 45 | + Verify the successful transfer of your data before you switch your |
| 46 | + application to the destination cluster. |
| 47 | + |
| 48 | +:ref:`c2c-release-version-numbers` |
| 49 | + Understand the semantic versioning of ``mongosync``. |
| 50 | + |
7 | 51 | .. toctree::
|
8 | 52 | :titlesonly:
|
9 | 53 |
|
|
0 commit comments