Skip to content

Remove "Oplog replay for storage level snapshots" #362

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

Open
boris-ilijic wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove "Oplog replay for storage level snapshots" #362

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 0 additions & 18 deletions docs/usage/oplog-replay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,24 +57,6 @@ After you [restored a physical backup](restore.md), do the following:

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

## Oplog replay for storage level snapshots

When making a backup, Percona Backup for MongoDB stops the point-in-time recovery. This is done to maintain data consistency after the restore.

Storage-level snapshots are saved with point-in-time recovery enabled. Thus, after the database restore from such a backup, point-in-time recovery is automatically enabled and starts oplog slicing. These new oplog slices might conflict with the existing oplogs saved during the backup. To replay the oplog in such a case, do the following after the restore:


1. Disable point-in-time recovery.
2. Delete the oplog slices that might have been created.
3. Re-sync the data from the storage.
4. Run the `pbm oplog-replay` command and specify the `--start` and `--end` flags with the timestamps.

```bash
pbm oplog-replay --start="2022-01-02T15:00:00" --end="2022-01-03T15:00:00"
```

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

[Known limitations](../features/known-limitations.md#oplog-replay-from-arbitrary-start-time){.md-button}
Comment on lines 58 to 60
Copy link

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By removing the dedicated “storage level snapshots” section, this page no longer explains the storage-level snapshot scenario, but the introduction still states oplog replay can be done on top of “storage level snapshot” backups. Please either (a) update the intro to drop/qualify that claim, or (b) replace the removed section with a brief note clarifying that no extra post-restore PITR/oplog-slice cleanup steps are required anymore (per current PBM behavior), and link to the relevant restore/PITR docs.

Copilot uses AI. Check for mistakes.


Loading