percona · nastena1606 · Sep 25, 2025 · Sep 16, 2025 · Sep 18, 2025 · Sep 22, 2025
diff --git a/diff.txt b/diff.txt
diff --git a/docs/_templates/pdf_cover_page.tpl b/docs/_templates/pdf_cover_page.tpl
@@ -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>
diff --git a/docs/details/gcs.md b/docs/details/gcs.md
@@ -9,6 +9,12 @@ You can use Google Cloud Storage (GCS) as a remote backup storage for Percona Ba
 
 PBM supports communication with GCS via the JSON API and XML API. The preferred approach is to use the JSON API with a service account. HMAC keys are mainly useful for compatibility with S3-style APIs.
 
+!!! warning "Known limitation"
+
+    When you run backups to GCS via HMAC keys, incomplete backups may be incorrectly marked as successful if network interruptions occur during the backup process. This results in corrupted or partially uploaded archives being stored and treated as valid backups, which can later fail during restore operations. This issue is addressed in [PBM-1605](https://perconadev.atlassian.net/browse/PBM-1605). 
+
+    Until the issue is resolved, we recommend using a native GCS connection type with JSON keys rather than HMAC keys to ensure backup integrity.
+
 To use GCS, you need the following:
 
 * [create a service account :octicons-link-external-16:](https://cloud.google.com/iam/docs/service-accounts-create#iam-service-accounts-create-console) 

diff --git a/docs/details/versions.md b/docs/details/versions.md
@@ -21,6 +21,7 @@ The Restore compatibility column indicates if you can restore from the backup ma
 
 | PBM version | Logical | Physical |Incremental physical | Restore backward compatibility|
 | ----------- |---------|----------|---------------------|---------------------|
+| **2.11.0** | [7.0.x], [8.0.x] | [7.0.x], [8.0.x] | [7.0.x], [8.0.x] | Yes |
 | **2.8.0 - 2.10.0**  | [6.0.x], [7.0.x], [8.0.x] | [6.0.x], [7.0.x], [8.0.x] | [6.0.x], [7.0.x], [8.0.x] | Yes |
 | **2.6.0 - 2.7.0** | [5.0.x], [6.0.x], [7.0.x] | [5.0.x], [6.0.x], [7.0.x] | [5.0.14-12], [6.0.3-2] and higher, [7.0.x] | Yes |
 | **2.2.0 - 2.5.0** | [4.4.x] and higher| [4.4.6-8] and higher, 5.0.x, 6.0.x| [4.4.18-18], [5.0.14-12], [6.0.3-2] and higher| Yes |
@@ -36,6 +37,7 @@ The Restore compatibility column indicates if you can restore from the backup ma
 
 | PBM version | Logical backups | Restore backward compatibility|
 | ----------- |-----------------| ----------------------------- |
+| **2.11.0** | 7.0.x and higher | Yes |
 | **2.8.0 - 2.10.0**  | 6.0.x and higher | Yes |
 | **2.6.0 - 2.7.0** | 5.0.x and higher | Yes |
 | **2.2.0 - 2.5.0** | 4.4.x and higher | Yes |

diff --git a/docs/release-notes.md b/docs/release-notes.md
@@ -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)

diff --git a/docs/release-notes/2.11.0.md b/docs/release-notes/2.11.0.md
@@ -0,0 +1,43 @@
+# Percona Backup for MongoDB 2.11.0 ({{date.2_11_0}})
+
+[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.
+
+## Release Highlights
+
+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 size. Learn more about how to do it in the [documentation](../features/split-merge-backup.md).
+
+## Dropped support of MongoDB 6.0
+
+Percona Backup for MongoDB drops support of MongoDB 6.0. Existing functionality in Percona Backup for MongoDB remains compatible with MongoDB 6.0 and Percona Server for MongoDB 6.0; however, further enhancements and bug fixes are no longer tested against this version.
+
+## Known limitations for using HMAC keys on GCS
+
+In PBM version 2.10.0 and higher, when you run backups to GCS via HMAC keys, incomplete backups may be incorrectly marked as successful if network interruptions occur during the backup process. This results in corrupted or partially uploaded archives being stored and treated as valid backups, which can later fail during restore operations. This issue is addressed in [PBM-1605](https://perconadev.atlassian.net/browse/PBM-1605). Until the issue is resolved, we recommend using a native GCS connection type with JSON keys rather than HMAC keys to ensure backup integrity.
+
+## 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-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.
+- [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.
+- [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.
+
+
+
+
diff --git a/mkdocs-base.yml b/mkdocs-base.yml
@@ -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
         - release-notes/2.8.0.md
         - release-notes/2.7.0.md
         - release-notes/2.6.0.md

diff --git a/variables.yml b/variables.yml
@@ -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