[DOCS-6618] Recommendations for restoring a single database using CM Created: 19/Nov/15  Updated: 27/Jul/16  Resolved: 17/May/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Joanna Cheng Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-7005 Comment on: "mms/tutorial/restore-sin... Closed
related to DOCS-5924 Update MMS restore docs as --dbpath i... Closed
Participants:
Days since reply: 8 years, 13 weeks ago
Epic Link: docs-restore-data
Story Points: 3

 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

Generated at Thu Feb 08 07:52:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.