-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:None
This has some implications in virtually every backup guide where fsyncLock is mentioned.
Most notably copying the data files using cp or taking filesystem snapshots when the journal is not on the same volume. We should think up what the new procedure should be and update the pages accordingly.
We should also determine if it is still unsafe to snapshot with no journal on the volume (or if it even is safe WITH a journal). If it is, I imagine we will just have to shutdown a secondary and stop writes to the system that way before taking the snapshot. But there may be a better way.
- related to
-
DOCS-4652 Update fsync documentation to clarify that lock=true does not mean data is not in motion on WT
- Closed
-
SERVER-16565 FsyncLock on WT should not imply "snapshotting" is OK
- Closed