Skip to content

Commit b1feb2e

Browse files
authored
Add note about shard binding (#5129) (#5133)
1 parent b9c3e02 commit b1feb2e

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

source/tutorial/assign-snapshot-stores-to-data-center.txt

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,19 @@ first store. There are times where these stores need to be deployed to
1919
other data centers due to either network performance issues or
2020
regulatory requirements.
2121

22-
You can bind specific |onprem| :term:`groups <group>` to specific
22+
You can bind specific |onprem| :term:`projects <project>` to specific
2323
snapshot stores and particular data centers. This assigns the backups
2424
of particular MongoDB deployments to specific data centers.
2525

26+
.. note::
27+
28+
You can bind only projects to specific snapshot stores or
29+
data centers. You cannot bind shards to a specific location.
30+
2631
.. include:: /images/dual-data-center-backup.rst
2732

2833
This tutorial sets up two snapshot stores, one in each of two separate
29-
data centers, and attaches a separate group to each.
34+
data centers, and attaches a separate project to each.
3035

3136
Prerequisites
3237
-------------
@@ -96,7 +101,7 @@ Install the |application| in each data center.
96101
.. important::
97102
Each set of installation instructions for each operating system
98103
covers how to create a multiple instances of an |application|. These
99-
activities need to be completed before binding groups to the backup
104+
activities need to be completed before binding projects to the backup
100105
resources.
101106

102107
Bind Projects to Backup Resources

0 commit comments

Comments
 (0)