-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Cloud Manager, Ops Manager
-
Labels:
-
Environment:
*Location*: https://docs.opsmanager.mongodb.com/v2.0/tutorial/restore-single-database/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36
*Referrer*: https://jira.mongodb.org/browse/CS-27330
*Screen Resolution*: 2560 x 1440
*repo*: REPONAME
*source*: tutorial/restore-single-database
*Location*: https://docs.opsmanager.mongodb.com/v2.0/tutorial/restore-single-database/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36 *Referrer*: https://jira.mongodb.org/browse/CS-27330 *Screen Resolution*: 2560 x 1440 *repo*: REPONAME *source*: tutorial/restore-single-database
As described in the yellow box on the beginning of this documentation page, mongodump --dbpath is not available anymore starting from MongoDB 3.0.
However the section Restore the Database, step 1 uses "mongodump --dbpath".
It may be worth mentioning that you can use the mongodump tool from MongoDB 2.6 only if the Backup was using MMAPv1. For WT backups this will not be possible.
Kind regards,
Emilio
- is related to
-
DOCS-6618 Recommendations for restoring a single database using CM
- Closed
- links to