-
Notifications
You must be signed in to change notification settings - Fork 23
PBM-1616 Release notes 2.11.0 #301
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.
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
Changes from 1 commit
977ba0b
1ab8332
95f0022
f532afa
263ee77
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| # Percona Backup for MongoDB 2.11.0 ({{date.2_11_0}}) | ||
|
Check notice on line 1 in docs/release-notes/2.11.0.md
|
||
|
|
||
| [Installation](../installation.md){.md-button} | ||
|
|
||
|
|
||
| Percona Backup for MongoDB is a distributed, low-impact solution for creating consistent backups of MongoDB sharded clusters and replica sets, and for restoring those backups to a specific point in time. | ||
|
Check failure on line 6 in docs/release-notes/2.11.0.md
|
||
|
|
||
| ## Release Highlights | ||
|
Check warning on line 8 in docs/release-notes/2.11.0.md
|
||
|
|
||
| This release provides the following features and improvements: | ||
|
|
||
| ## Ensure successful upload of any size backup | ||
|
|
||
| When backup files are so large that they exceed the object size limit for backup storage, PBM now splits such files into pieces that fall within the size limit and uploads them to the storage. PBM names these pieces to identify and manage them later. The reverse process occurs during the data read for a restore: PBM merges the pieces into a single file and proceeds with the command execution. You can redefine the default size limit using PBM configuration and ensure your backups are uploaded regardless of the storage. Learn more about how to do it in the [documentation](../features/split-merge-backup.md). | ||
|
Check warning on line 14 in docs/release-notes/2.11.0.md
|
||
|
|
||
| ## Changelog | ||
|
|
||
| ## Improvements | ||
|
|
||
| - [PBM-1490](https://perconadev.atlassian.net/browse/PBM-1490): Physical backups now automatically split and reassemble very large files, preventing failures when uploading to storage with size limits. | ||
| - [PBM-1562](https://perconadev.atlassian.net/browse/PBM-1562): Provided a complete Percona Backup for MongoDB configuration example for easier and more accurate setup. | ||
| - [PBM-1597](https://perconadev.atlassian.net/browse/PBM-1597): PBM now displays more specific error messages when your MongoDB version is incompatible, guiding you on whether to upgrade MongoDB or PBM. | ||
|
|
||
| ## Fixed bugs | ||
|
|
||
| - [PBM-1497](https://perconadev.atlassian.net/browse/PBM-1497): Point-in-Time Recovery (PITR) now accurately reports failure when oplog replay encounters errors. | ||
|
Check notice on line 26 in docs/release-notes/2.11.0.md
|
||
| - [PBM-1569](https://perconadev.atlassian.net/browse/PBM-1569): The `pbm restore` command now displays a clear message when required arguments are missing, rather than a confusing parsing error. | ||
| - [PBM-1574](https://perconadev.atlassian.net/browse/PBM-1574): The `pbm restore -w` command now correctly waits until the entire restore process is complete. | ||
| - [PBM-1581](https://perconadev.atlassian.net/browse/PBM-1581): Security has been enhanced for services connecting with Google. | ||
|
Check notice on line 29 in docs/release-notes/2.11.0.md
|
||
| - [PBM-1583](https://perconadev.atlassian.net/browse/PBM-1583): PBM now keeps all routing collections in the target cluster and clears contents in all of them except the `config.system.sessions` collection during logical restores to avoid the "Time monotonicity violation" error | ||
| - [PBM-1591](https://perconadev.atlassian.net/browse/PBM-1591): Logical backups now complete successfully even when time series collections share the same name across different databases. | ||
| - [PBM-1604](https://perconadev.atlassian.net/browse/PBM-1604): PBM CLI now correctly waits for restore completion in single-node replica set setups without reporting false errors. | ||
|
Check warning on line 32 in docs/release-notes/2.11.0.md
|
||
| - [PBM-1605](https://perconadev.atlassian.net/browse/PBM-1605): Backups that fail to complete are now correctly marked as failures, preventing misleading successful statuses. | ||
|
|
||
|
|
||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The navigation structure is inconsistent. The 2.11.0 entry uses the full template format with name and date, while older entries (2.10.0, 2.9.1, 2.9.0) only reference the file path. All entries should follow the same format for consistency.