Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-6618

Recommendations for restoring a single database using CM

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Cloud Manager, Ops Manager
    • 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

      Attachments

        Activity

          People

            tony.sansone@mongodb.com Anthony Sansone (Inactive)
            joanna.cheng@mongodb.com Joanna Cheng
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              8 years, 13 weeks ago