determine storageEngine specificity in docs (DOCS-4856)

[DOCS-5710] Update backup procedure for WiredTiger (via filesystem) Created: 23/Jun/15  Updated: 11/Jan/17  Resolved: 29/Oct/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Sub-task Priority: Major - P3
Reporter: Jason Zucchetto Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-5604 Comment on: "manual/core/replica-set-... Closed
Participants:
Days since reply: 8 years, 15 weeks, 6 days ago

 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.



 Comments   
Comment by Githook User [ 29/Oct/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-5074 DOCS-5039 DOCS-6350 WT storage engine and journaling

DOCS-5710 DOCS-5604 WT and fsynclock

DOCS-5755 WT stats part 1
Branch: master
https://github.com/mongodb/docs/commit/128a3844e55b4aeb707ed97b5bce08d7b787ca6d

Generated at Thu Feb 08 07:50:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.