Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
*Location*: https://docs.mms.mongodb.com/tutorial/restore-single-database/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36
*Referrer*: https://docs.mms.mongodb.com/tutorial/restore-replica-set/
*Screen Resolution*: 1920 x 1080
*repo*: REPONAME
*source*: tutorial/restore-single-database
*Location*: https://docs.mms.mongodb.com/tutorial/restore-single-database/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36 *Referrer*: https://docs.mms.mongodb.com/tutorial/restore-replica-set/ *Screen Resolution*: 1920 x 1080 *repo*: REPONAME *source*: tutorial/restore-single-database
Description
WIth MongoDB 3.0 it's no longer possible to use "dbpath" and "directoryperdb" option with mongodump (http://docs.mongodb.org/manual/reference/program/mongodump/#options).
Our documentation for how to restore a single database needs to be updated.
This is particularly important for WiredTiger.
We do not currently provide restore'd backup snapshots using directoryPerDB and related settings meaning in order to restore to directoryPerDB with WiredTiger an extra dump-> load phase is required.
Attachments
Issue Links
- is related to
-
DOCS-5575 Comment on: "mms/tutorial/restore-single-database.txt"
-
- Closed
-