Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-4856 determine storageEngine specificity in docs
  3. DOCS-5710

Update backup procedure for WiredTiger (via filesystem)

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 01112017-cleanup
    • Component/s: None
    • Labels:
      None
    • Last comment by Customer:
      true

      Description

      There are conflicting statements in the docs for backups regarding WiredTiger.

      This page references db.fsyncLock() and db.fsyncUnlock():
      http://docs.mongodb.org/manual/tutorial/backup-sharded-cluster-with-filesystem-snapshots/#if-necessary-lock-one-secondary-member-of-each-replica-set-in-each-shard

      But when you dig further into db.fsyncLock for WiredTiger:
      http://docs.mongodb.org/manual/reference/method/db.fsyncLock/#compatibility-with-wiredtiger

      "With WiredTiger the db.fsyncLock() and db.fsyncUnlock() operations cannot guarantee that the data files do not change. As a result, do not use these methods to ensure consistency for the purposes of creating backups."

      We should outline the exact procedure for a filesystem backup with WiredTiger, this is pretty heavily referenced in training/consulting.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              jason.zucchetto Jason Zucchetto
              Participants:
              Last commenter:
              Jonathan Dahl Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                6 years, 5 weeks, 4 days ago
                Date of 1st Reply: