Skip to content

Explain what --oplogReplay really does. #2164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Explain what --oplogReplay really does. #2164

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0607818
Explain what --oplogReplay really does.
drmirror Feb 11, 2015
5b08c76
Fix typo
drmirror Feb 12, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions source/includes/options-mongorestore.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,6 +257,15 @@ description: |
current state of the database reflects the point-in-time backup captured
with the ":option:`mongodump --oplog`" command. For an example of
{{role}}, see :ref:`backup-restore-oplogreplay`.

To find the oplog entries it should replay, mongorestore looks for a
file named oplog.bson immediately below the dump directory. This is
where ":option:`mongodump --oplog`" places the oplog that it generates,
but you can place any oplog there, for example a dump of an existing
oplog that you created with mongodump (in this case, the oplog will likely
be dumped under the name oplog.rs.bson, and you will have to rename it to
oplog.bson and place it into the top-level directory of the dump in
order for mongorestore to replay it).
optional: true
---
program: mongorestore
Expand Down