Skip to content
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

Jump to bottom

Fixed paths to links #131

Merged
merged 1 commit into from
Aug 1, 2023
Merged

Fixed paths to links #131

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
4 changes: 2 additions & 2 deletions docs/usage/pitr-tutorial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ When point-in-time recovery is started, Percona Backup for MongoDB uses the prov

## From physical backups

Starting with version [2.2.0](../release-notes-2.2.0.md), you can recover your database from a full or an incremental physical backup in the same automated fashion as from a logical one. Percona Backup for MongoDB restores the backup snapshot and automatically replays the oplog events on top of it up to the specified time, guaranteeing data consistency. This helps you prevent data loss during a disaster and gives you the same user experience when managing backups and restores.
Starting with version [2.2.0](../release-notes/2.2.0.md), you can recover your database from a full or an incremental physical backup in the same automated fashion as from a logical one. Percona Backup for MongoDB restores the backup snapshot and automatically replays the oplog events on top of it up to the specified time, guaranteeing data consistency. This helps you prevent data loss during a disaster and gives you the same user experience when managing backups and restores.

To restore a database from a physical backup, specify the time and the base backup for the [`pbm restore`](../reference/pbm-commands.md#pbm-restore) command:

Expand Down Expand Up @@ -131,7 +131,7 @@ After the point-in-time recovery is complete, perform these post-restore steps:

5. Make a fresh backup to serve as the new base for future restores.

6. [Enable point-in-time routine](point-in-time-recovery.md#enable-point-in-time-recovery) to resume saving oplog slices.
6. [Enable point-in-time routine](../features/point-in-time-recovery.md#enable-point-in-time-recovery) to resume saving oplog slices.

For Percona Backup for MongoDB version 2.1.0 and earlier, point-in-time recovery consists of the following steps:

Expand Down