Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
Description
The note on https://docs.cloud.mongodb.com/tutorial/restore-single-database/ currently says
MongoDB 3.0 introduced major changes to the MongoDB tools in order to support additional storage engines such as WiredTiger. In MongoDB 3.0, mongodump and mongorestore do not support the --dbpath option. As such, you cannot use this procedure for a partial data restore on a mongod running MongoDB 3.0.
If you anticipate you will want to restore a single database, create a backup for just that database by excluding the databases or collections that you do not want to back up using the Blacklist field in the Advanced Settings.
I don't consider this a good workaround because
- This doesn't cover the case where the user wants a one-off restore (it addresses the use case where they consistently don't care about some of their data)
- You no longer get seedSecondary if you exclude collections
- It requires a resync
- You can get around this by just starting a mongod against the restore, to then dump the relevant database