-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
modified: docs/release-notes/2.0.4.md modified: docs/release-notes/2.3.0.md modified: mkdocs-base.yml modified: mkdocs-pdf.yml modified: variables.yml
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Percona Backup for MongoDB 2.3.0 (2023-09-25) | ||
Check notice on line 1 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L1
Raw output
|
||
|
||
[Installation](../installation.md){.md-button} | ||
|
||
|
||
Percona Backup for MongoDB is a distributed, low-impact solution for consistent backups of MongoDB sharded clusters and replica sets. This is a tool for creating consistent backups across a MongoDB sharded cluster (or a non-sharded replica set), and for restoring those backups to a specific point in time. | ||
Check notice on line 6 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L6
Raw output
|
||
|
||
## Release Highlights | ||
Check warning on line 8 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L8
Raw output
|
||
|
||
* The support for MongoDB 4.2 is deprecated. Existing functionality in Percona Backup for MongoDB remains compatible with MongoDB 4.2 and Percona Server for MongoDB 4.2; however, further enhancements and bug fixes are no longer tested against this version. | ||
Check notice on line 10 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L10
Raw output
Check warning on line 10 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L10
Raw output
|
||
* The ability to [view the backup contents](../usage/describe-backup.md) improves troubleshooting of backups in environments where databases are often created and / or dropped. | ||
* The ability to [make physical backups in mixed deployments](../features/physical.md#physical-backups-in-mixed-deployments) with MongoDB Community and Percona Server for MongoDB (PSMDB) nodes streamlines the backup flow for organizations that are still evaluating or migrating their data sets against PSMDB. | ||
Check notice on line 12 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L12
Raw output
Check notice on line 12 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L12
Raw output
Check notice on line 12 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L12
Raw output
|
||
* Improved validation of a base backup snapshot for point-in-time recovery aligns the recovery flow for logical and physical backups. | ||
|
||
### Supported platforms changes | ||
|
||
* A Docker image for Percona Backup for MongoDB is now available for ARM64 architectures. This improves the user experience with PBM for developers with ARM-based MacBooks. | ||
Check notice on line 17 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L17
Raw output
|
||
* Percona Backup for MongoDB packages are now available for Debian 12 (bookworm). | ||
Check notice on line 18 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L18
Raw output
|
||
|
||
## New Features | ||
Check warning on line 20 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L20
Raw output
|
||
|
||
* [PBM-848](https://jira.percona.com/browse/PBM-848) - List databases and collections from backup | ||
|
||
## Improvements | ||
|
||
* [PBM-1147](https://jira.percona.com/browse/PBM-1147), [PBM-885](https://jira.percona.com/browse/PBM-885) - Support symlinks as the `path` for filesystem storage type and properly retrieve data during resync | ||
Check failure on line 26 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L26
Raw output
|
||
* [PBM-1162](https://jira.percona.com/browse/PBM-1162), [PBM-1166](https://jira.percona.com/browse/PBM-1166) - Improve validation of physical and incremental backups as the base for point-in-time recovery | ||
* [PBM-1171](https://jira.percona.com/browse/PBM-1171) - Add ability to make physical backups in mixed deployments | ||
|
||
## Bugs Fixed | ||
Check warning on line 30 in docs/release-notes/2.3.0.md GitHub Actions / vale[vale] docs/release-notes/2.3.0.md#L30
Raw output
|
||
|
||
* [PBM-1161](https://jira.percona.com/browse/PBM-1161) - Rebuild indexes only for the selected namespaces after selective restore | ||
* [PBM-1173](https://jira.percona.com/browse/PBM-1173), [PBM-1180](https://jira.percona.com/browse/PBM-1180) - Fixed the issue with the primary node crash after the point-in-time recovery from physical backup | ||
* [PBM-1176](https://jira.percona.com/browse/PBM-1176) - Fixed the decoding of the physical restore metadata to ensure correct output of the `pbm describe-restore` command | ||
* [PBM-1181](https://jira.percona.com/browse/PBM-1181) - Fixed the issue with logical restore failure by excluding the `config.changelog` collection from the restore | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
# PBM Variables set for HTML output | ||
# See also mkdocs.yml plugins.with-pdf.cover_subtitle and output_path | ||
|
||
release: '2.2.1' | ||
version: '2.2' | ||
release_date: 2023-07-27 | ||
release: '2.3.0' | ||
version: '2.3' | ||
|