From a4ab4c6656fec8d1f798c9a033b6a607f7f72672 Mon Sep 17 00:00:00 2001 From: Norman Graham Date: Wed, 5 Feb 2014 20:24:28 +0000 Subject: [PATCH] Update journaling.txt note to use fsyncLock / fsyncUnlock for snapshots when database and journal files are on separate physical media --- source/core/journaling.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/source/core/journaling.txt b/source/core/journaling.txt index 9e28da2fad8..474d9240888 100644 --- a/source/core/journaling.txt +++ b/source/core/journaling.txt @@ -41,8 +41,11 @@ different filesystem. .. important:: If you place the journal on a different filesystem from your data - files you *cannot* use a filesystem snapshot to capture valid - backups of a :setting:`dbpath` directory. + files you *cannot* use a filesystem snapshot alone to capture valid + backups of a :setting:`dbpath` directory. In this case, use + :method:`~db.fsyncLock()` to ensure that database files are consistent + before the snapshot and :method:`~db.fsyncUnlock()` once the snapshot + is complete. .. note::