Skip to content

Update oplog-replay.md #323

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

Merged
nastena1606 merged 5 commits into from
Dec 4, 2025
Merged

Update oplog-replay.md #323

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5a6bdc9
Update oplog-replay.md
igroene Dec 3, 2025
2af4ed8
Update docs/usage/oplog-replay.md
igroene Dec 3, 2025
56b9446
Added a section with the explanatio
nastena1606 Dec 3, 2025
41197f9
Updated after the review
nastena1606 Dec 3, 2025
c65dedc
Removed confusing sentence
nastena1606 Dec 3, 2025
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
5 changes: 5 additions & 0 deletions docs/usage/oplog-replay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,11 @@ After you [restored a physical backup](restore.md), do the following:
```bash
pbm oplog-replay --start="2022-01-02T15:00:00" --end="2022-01-03T15:00:00"
```

!!! note ""

Another possibility is using MongoDB’s (epoch, ordinal) values directly.
For example, it is possible to use `pbm oplog-replay --end “1764576382,0”` or `--end “1764576382,100”` so it’s possible to specify up to the exact operation you need to apply in the oplog.

4. After the oplog replay, make a fresh backup and enable the point-in-time recovery oplog slicing.

Expand Down