Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
1 change: 0 additions & 1 deletion diff.txt

This file was deleted.

4 changes: 2 additions & 2 deletions docs/_templates/pdf_cover_page.tpl
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
<p>
<img src="_images/Percona_Logo_Color.png" />
</p>
<h1>Backup for MongoDB 2.10.0</h1>
<h1>Backup for MongoDB 2.11.0</h1>
{% if config.site_description %}
<h1>{{ config.site_description }}</h1>
{% endif %}
<h2>2.10.0 (June 26, 2025)</h2>
<h2>2.11.0 (September 25, 2025)</h2>
1 change: 1 addition & 0 deletions docs/release-notes.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
# {{pbm.full_name}} release notes

* [{{pbm.full_name}} 2.11.0](release-notes/2.11.0.md)
* [{{pbm.full_name}} 2.10.0](release-notes/2.10.0.md)
* [{{pbm.full_name}} 2.9.1](release-notes/2.9.1.md)
* [{{pbm.full_name}} 2.9.0](release-notes/2.9.0.md)
Expand Down
37 changes: 37 additions & 0 deletions docs/release-notes/2.11.0.md
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

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L1

[Google.Parens] Use parentheses judiciously.
Raw output
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 1, "column": 37}}}, "severity": "INFO"}

[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

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L6

[Vale.Spelling] Did you really mean 'sharded'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'sharded'?", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 6, "column": 109}}}, "severity": "ERROR"}

## Release Highlights

Check warning on line 8 in docs/release-notes/2.11.0.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L8

[Google.Headings] 'Release Highlights' should use sentence-style capitalization.
Raw output
{"message": "[Google.Headings] 'Release Highlights' should use sentence-style capitalization.", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 8, "column": 4}}}, "severity": "WARNING"}

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

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L14

[Google.Colons] ': P' should be in lowercase.
Raw output
{"message": "[Google.Colons] ': P' should be in lowercase.", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 14, "column": 313}}}, "severity": "WARNING"}

Check notice on line 14 in docs/release-notes/2.11.0.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L14

[Google.Passive] In general, use active voice instead of passive voice ('are uploaded').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are uploaded').", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 14, "column": 485}}}, "severity": "INFO"}

## 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

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L26

[Google.Parens] Use parentheses judiciously.
Raw output
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 26, "column": 88}}}, "severity": "INFO"}
- [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

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L29

[Google.Passive] In general, use active voice instead of passive voice ('been enhanced').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('been enhanced').", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 29, "column": 78}}}, "severity": "INFO"}
- [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

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/release-notes/2.11.0.md#L32

[Google.WordList] Use 'command-line tool' instead of 'CLI'.
Raw output
{"message": "[Google.WordList] Use 'command-line tool' instead of 'CLI'.", "location": {"path": "docs/release-notes/2.11.0.md", "range": {"start": {"line": 32, "column": 69}}}, "severity": "WARNING"}
- [PBM-1605](https://perconadev.atlassian.net/browse/PBM-1605): Backups that fail to complete are now correctly marked as failures, preventing misleading successful statuses.




7 changes: 4 additions & 3 deletions mkdocs-base.yml
Original file line number Diff line number Diff line change
Expand Up @@ -272,9 +272,10 @@ nav:
- Release notes:
- release-notes.md
- PBM 2.x:
- "{{pbm.full_name}} 2.10.0 ({{date.2_10_0}})": release-notes/2.10.0.md
- "{{pbm.full_name}} 2.9.1 ({{date.2_9_1}})": release-notes/2.9.1.md
- "{{pbm.full_name}} 2.9.0 ({{date.2_9_0}})": release-notes/2.9.0.md
- "{{pbm.full_name}} 2.11.0 ({{date.2_11_0}})": release-notes/2.11.0.md
- release-notes/2.10.0.md
- release-notes/2.9.1.md
- release-notes/2.9.0.md
Comment on lines +275 to +278
Copy link

Copilot AI Sep 16, 2025

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.

Copilot uses AI. Check for mistakes.
- release-notes/2.8.0.md
- release-notes/2.7.0.md
- release-notes/2.6.0.md
Expand Down
5 changes: 3 additions & 2 deletions variables.yml
Original file line number Diff line number Diff line change
@@ -1,13 +1,14 @@
# PBM Variables set for HTML output
# See also mkdocs.yml plugins.with-pdf.cover_subtitle and output_path

release: '2.10.0'
version: '2.10'
release: '2.11.0'
version: '2.11'
year: '2025'

pbm:
full_name: 'Percona Backup for MongoDB'
date:
2_11_0: 2025-09-25
2_10_0: 2025-06-26
2_9_1: 2025-03-27
2_9_0: 2025-02-19
Expand Down