|
| 1 | +# Percona Backup for MongoDB 2.0.1 (2022-10-12) |
| 2 | + |
| 3 | +| Release date | October 12, 2022 | |
| 4 | +|------------- | ---------------| |
| 5 | +| Installation | [Installing Percona Backup for MongoDB](../installation.md) | |
| 6 | + |
| 7 | + |
| 8 | +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. |
| 9 | + |
| 10 | +## Release Highlights |
| 11 | + |
| 12 | +* The support of [server-side encryption with customer-provided keys managed on the customer side (SSE-C)](../details/storage-configuration.md#server-side-encryption) enables you to use the S3-compatible storage of your choice thus preventing the vendor lock-in and saving your costs on AWS KMS (Key Management Service). |
| 13 | +* The ability to [configure Percona Backup for MongoDB remotely](../manage/configure-remotely.md) simplifies its management when PBM is deployed in Docker, Kubernetes or other cloud services. |
| 14 | +* The ability to configure the sidecar mode for Percona Backup for MongoDB improves its operation as part of [Kubernetes Operator for MongoDB](https://docs.percona.com/percona-operator-for-mongodb/index.html). |
| 15 | +* Troubleshooting enhancements: |
| 16 | + |
| 17 | + - The ability to [define a timezone for logs and to follow the logs dynamically](../reference/pbm-commands.md#pbm-logs). |
| 18 | + - Indication of arbiter nodes as non-supported ones in `pbm status` output |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | +## New Features |
| 23 | + |
| 24 | +- [PBM-733](https://jira.percona.com/browse/PBM-733): Allow changing the timezone of logs in PBM |
| 25 | +- [PBM-877](https://jira.percona.com/browse/PBM-877): Enable PBM to read the config file from stdin |
| 26 | + |
| 27 | +## Improvements |
| 28 | + |
| 29 | +- [PBM-949](https://jira.percona.com/browse/PBM-949): Improve handling of arbiter nodes |
| 30 | +- [PBM-948](https://jira.percona.com/browse/PBM-948): Align `pbm describe-backup` and `pbm describe-restore` outputs |
| 31 | +- [PBM-941](https://jira.percona.com/browse/PBM-941): Add a sidecar mode for PBM to prevent the database crash when a `pbm-agent` is misconfigured in a container |
| 32 | +- [PBM-922](https://jira.percona.com/browse/PBM-922): Add support for SSE-C for S3 providers (Thanks to Richard Bateman for reporting this issue and contributing to it) |
| 33 | +- [PBM-897](https://jira.percona.com/browse/PBM-897): Add the ability to dynamically follow PBM logs |
| 34 | + |
| 35 | + |
| 36 | +## Bugs Fixed |
| 37 | + |
| 38 | +- [PBM-978](https://jira.percona.com/browse/PBM-978): Fixed the physical restore on replica sets having hidden nodes |
| 39 | +- [PBM-975](https://jira.percona.com/browse/PBM-975): Fixed the issue with the display of point-in-time recovery chunks without base snapshot after storage resync |
| 40 | +- [PBM-966](https://jira.percona.com/browse/PBM-966): Fixed the error handling of point-in-time recovery to non-existent timestamp by `pbm-agents` |
| 41 | +- [PBM-858](https://jira.percona.com/browse/PBM-858): Improve reporting of the error when an oplog chunk can't be created due to insufficient range |
0 commit comments