Skip to content

Commit 20bceed

Browse files
author
Sam Kleinman
committed
DOCS-854: correction about snapshot behavior
1 parent 74d8525 commit 20bceed

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

source/tutorial/backup-databases-with-filesystem-snapshots.txt

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -230,8 +230,12 @@ The above sequence does the following:
230230
.. note::
231231

232232
The restored snapshot will have a stale ``mongod.lock`` file. If
233-
you do not remove this file from the snapshot, MongoDB will assume
234-
that the stale lock file indicates an unclean shutdown.
233+
you do not remove this file from the snapshot, and MongoDB may
234+
assume that the stale lock file indicates an unclean shutdown. If
235+
you're running with :setting:`journal` enabled, and you *do not*
236+
use :method:`db.fsyncLock()`, you do not need to remove the
237+
``mongod.lock`` file. If you use :method:`db.fsyncLock()` you will
238+
need to remove the lock.
235239

236240
.. _backup-restore-from-snapshot:
237241

0 commit comments

Comments
 (0)