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

PBM-1136 - Fix supported versions for incremental backups #122

Merged
merged 2 commits into from
Jul 4, 2023
Merged

PBM-1136 - Fix supported versions for incremental backups #122

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b74fa1
Fix supported versions
sleto-it Jul 4, 2023
e9044c9
nastena's feedback
sleto-it Jul 4, 2023
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
2 changes: 1 addition & 1 deletion docs/features/incremental-backup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
We recommend to make a new incremental base backup and start the incremental backup chain from it after the upgrade to Percona Backup for MongoDB 2.1.0

* Incremental backup implementation is based on the [`$backupCursor`](https://docs.percona.com/percona-server-for-mongodb/6.0/backup-cursor.html) aggregation stage that is available only in Percona Server for MongoDB. Therefore, you must be running Percona Server for MongoDB in your deployment to use incremental physical backups.
* Incremental backups are supported for Percona Server for MongoDB starting with the following versions: [4.2.24-24](https://docs.percona.com/percona-server-for-mongodb/4.2/release_notes/4.2.24-24.html), [4.4.18](https://docs.percona.com/percona-server-for-mongodb/4.4/release_notes/4.4.18-18.html), [5.0.2-1](https://docs.percona.com/percona-server-for-mongodb/5.0/release_notes/5.0.2-1.html), [6.0.2-1](https://docs.percona.com/percona-server-for-mongodb/6.0/release_notes/6.0.2-1.html) and higher.
* Incremental backups are supported for Percona Server for MongoDB starting with the following versions: [4.2.24-24](https://docs.percona.com/percona-server-for-mongodb/4.2/release_notes/4.2.24-24.html), [4.4.18](https://docs.percona.com/percona-server-for-mongodb/4.4/release_notes/4.4.18-18.html), [5.0.14-12](https://docs.percona.com/percona-server-for-mongodb/5.0/release_notes/5.0.14-12.html), [6.0.3-2](https://docs.percona.com/percona-server-for-mongodb/6.0/release_notes/6.0.3-2.html) and higher.

Check notice on line 12 in docs/features/incremental-backup.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/features/incremental-backup.md#L12 

[Google.Passive] In general, use active voice instead of passive voice ('are supported').
Raw output 
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are supported').", "location": {"path": "docs/features/incremental-backup.md", "range": {"start": {"line": 12, "column": 23}}}, "severity": "INFO"}
* Due to [WiredTger restrictions in Log-Structured Merge (LSM) trees](https://source.wiredtiger.com/develop/backup.html#backup_incremental-block) behavior when the `$backupCursor` is opened, incremental backups are not available if the LSM tree is configured in the database.

Owners of large datasets may need to back up data frequently. Making full physical backups every time is costly in terms of storage space. Incremental physical backups come in handy in this scenario, enabling you to optimize backup strategy and reduce storage costs.
Expand Down