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

Add warning about directoryPerDB not supported in restorations to OpsMgr doc, to match CloudMgr doc.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Ops Manager
    • Labels:
      None
    • # Replies:
      0
    • Last comment by Customer:
      true
    • Story Points:
      0.25
    • Sprint:
      Cloud Docs July 26: Holyoke, Docs Q2 W12

      Description

      A user ran into the problem where you cannot do a backup restoration if your live replica set is using the directoryPerDB option.

      On the /core/restore-overview/ page for Cloud Manager docs this warning was added:

      IMPORTANT

      Under certain conditions, an automated restore fails because either:

      1. The backup and destination databases’ storage engines do not match.
      2. The destination database uses settings that are not currently preserved in the backup itself.

      If the backup and destination database storage engines do not match, mongod cannot start once the backup is restored. At this time, you can either:

      1. Not restore this snapshot.
      2. Change the storage engine of the destination sharded cluster or replica set to match the configuration of the snapshot.

      If the destination database uses any of the following settings, an automated restore fails:

      • storage.directoryPerDB
      • security.enableEncryption (WiredTiger only)
      • storage.wiredTiger.engineConfig.directoryForIndexes (WiredTiger only)

      The user complained that it should be in the equivalent Ops Manager docs page (/v2.0/core/restore-overview/) too. So far as I see the advice is valid for Ops Manager too. Could it be added there too?

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since reply:
                  3 years, 27 weeks, 1 day ago
                  Date of 1st Reply: