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

Improve sharded cluster restoration instructions

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • v1.3.11
    • None
    • manual
    • None

    Description

      Regarding: http://docs.mongodb.org/manual/tutorial/restore-sharded-cluster/

      At present we provide separate instructions for creating sharded cluster backups using:

      1. Database snapshots
        1. http://docs.mongodb.org/manual/tutorial/backup-sharded-cluster-with-filesystem-snapshots/
      2. mongodump (not sure why there are 2)
        1. http://docs.mongodb.org/manual/tutorial/backup-sharded-cluster-with-database-dumps/
        2. http://docs.mongodb.org/manual/tutorial/backup-small-sharded-cluster-with-mongodump/

      When it comes to restoring a sharded cluster there is only one set of instructions:

      1. http://docs.mongodb.org/manual/tutorial/restore-sharded-cluster/

      The problem with having a single page is that it is hard to provide clear directions as the steps will differ depending on restore source. For example, to restore snapshots you want to put in place and then start mongod. For mongodumped files you typically want to start mongod first and then restore to the running process.

      Our current instructions are not clear on all aspects, for example the config server restoration assumes mongodumped files rather than snapshots.

      Please improve these instructions to be more clear for specific restore cases. It may be worth splitting into multiple pages as we do for the backup creation process. We should provide recipes for this that allow for a user to run through without having to second guess specific steps.

      Attachments

        Activity

          People

            bgrabar Bob Grabar
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              9 years, 22 weeks, 5 days ago