Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
*Location*: https://docs.opsmanager.mongodb.com/current/tutorial/configure-backup-data-locality/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36
*Referrer*: https://docs.opsmanager.mongodb.com/current/tutorial/add-existing-mongodb-processes/
*Screen Resolution*: 1920 x 1080
*repo*: REPONAME
*source*: tutorial/configure-backup-data-locality
*Location*: https://docs.opsmanager.mongodb.com/current/tutorial/configure-backup-data-locality/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36 *Referrer*: https://docs.opsmanager.mongodb.com/current/tutorial/add-existing-mongodb-processes/ *Screen Resolution*: 1920 x 1080 *repo*: REPONAME *source*: tutorial/configure-backup-data-locality
Description
This page incorrectly combines two concepts
1) Configuring >1 backup database
2) Using multiple backup databases to ascertain data locality in terms of where snapshots are stored
These are independent concepts (but 2 requires 1) yet the title and TOC are misleading