Details
-
Sub-task
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
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
- related to
-
DOCS-5604 Comment on: "manual/core/replica-set-hidden-member.txt"
-
- Closed
-