We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 74d8525 commit 20bceedCopy full SHA for 20bceed
source/tutorial/backup-databases-with-filesystem-snapshots.txt
@@ -230,8 +230,12 @@ The above sequence does the following:
230
.. note::
231
232
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.
+ you do not remove this file from the snapshot, and MongoDB may
+ 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.
239
240
.. _backup-restore-from-snapshot:
241
0 commit comments