Releases: percona/percona-backup-mongodb
v2.8.0
Release Highlights
Network routing control in communication of pbm-agents with the backup storage
You can now control how pbm-agents reach the same remote backup storage by defining custom endpoints for them. This way you respect the network settings of the data centers where the servers running pbm-agents reside and ensure the proper functioning of PBM. Custom endpoints are supported for AWS and Microsoft Azure Blob storages.
Simplified troubleshooting with restoring the same collection under a different name
Now you can restore a single collection under a different name up to a certain point in time alongside the current collection. The restored collection has the same data and indexes as the one you backed up. This makes it easier to compare the data in both collections and identify what caused the issue with the database. As a result, your troubleshooting efforts significantly reduce.
Reduced troubleshooting time with diagnostics report
Collect all information required to troubleshoot backups and restores in one go. Generate the comprehensive diagnostics report about an operation execution and either dive deep yourself or file a bug report to our experts and attach the diagnostics archive to it. This way you reduce the iteration time and speed up the issue resolution.
Improved log rotation with a custom path for log output
You can now output logging information from every pbm-agent to a file at a custom path. This way you can introduce log rotation, manage the system log effectively and comply to security regulations for logging and auditing.
Additional flexibility for backups
PBM no longer uses mongodump for making backups but uses its own dump implementation. This makes backup operations flexible as it lifts the mongodumps' limitations and opens space for further improvements.
Changes in supported MongoDB versions
Starting from this release, PBM supports Percona Server for MongoDB 8.0 and MongoDB Community 8.0.
At the same time, PBM no longer supports Percona Server for MongoDB 5.0 and MongoDB Community 5.0 as it entered the end-of-life stage. Existing functionality remains compatible with version 5.0. However, we will no longer test new features and improvements against this version.
Known limitation
Selective backups and restores fail for setups with config shards. Find more details in PBM-1465.
Changelog
For more details, please check out the full list of improvements
https://docs.percona.com/percona-backup-mongodb/release-notes/2.8.0.html
Join Percona Squad
Participate in monthly SWAG raffles, get an early access to new product features and invite-only “ask me anything” sessions with database performance experts. Interested? Fill in the form at https://squad.percona.com/mongodb
Contact Us
on Forums
by Email
or Professional Support
v2.7.0
Release Highlights
Single authentication point for PBM running in Amazon EKS
Now PBM running in Amazon Elastic Kubernetes Service (EKS) can access AWS services using the credentials from the IAM role associated with the service account that is assigned to the Pod where PBM is running. Since with this improvement you don’t have to pass the credentials to every individual Pods, the overall security of your infrastructure increases.
Consider the following limitation if you run Percona Operator for MongoDB: a restore does not work with this feature without the modification of default serviceAccount. It will be improved in future releases of the Operator to cover this case.
Changelog
For more details, please check out the full list of improvements
https://docs.percona.com/percona-backup-mongodb/release-notes/2.7.0.html
Join Percona Squad
Participate in monthly SWAG raffles, get an early access to new product features and invite-only “ask me anything” sessions with database performance experts. Interested? Fill in the form at https://squad.percona.com/mongodb
Contact Us
on Forums
by Email
or Professional Support
v2.6.0
Release Highlights
-
Multiple storages for backups and restores
You can now define multiple storages for making backups and instruct PBM on what storage to save a backup: on the main or on any additional (external) one. This ability helps you save on data transfer costs when using cloud storage, as well as enables you to follow closely with the requirements of your organization’s backup policy. -
Adjust node priority for point-in-time recovery oplog slicing
You can now redefine node priorities not only for making backups but also for point-in-time recovery oplog slices. For example, you can instruct PBM to save oplog slices either from a dedicated node or from nodes in the geographically closest location, thus reducing network latency. -
Additional control over PBM command execution
You can now configure the waiting time for a command execution by passing the --wait-time flag for the following commands:pbm config –force-resync –wait –wait-time='5m' pbm backup –wait –wait-time='5m' pbm restore –wait –wait-time='5m' pbm oplog-replay –wait –wait-time='5m' pbm profile add –sync –wait –wait-time='5m' pbm profile remove –wait –wait-time='5m' pbm profile sync –wait –wait-time='5m' pbm delete-pitr –older-than –wait –wait-time='5m' pbm cleanup –older-than –wait –wait-time='5m'This way you have more control over the PBM operation. This enhancement also improves the error logging.
-
Snapshot-based physical backups are generally available
With snapshot-based physical backups now generally available, you can use this functionality in production environments and enjoy all the benefits of faster restores from snapshots with almost immediate access to data. -
Dropped support of MongoDB 4.4
Percona Backup for MongoDB drops support of MongoDB 4.4. Existing functionality in Percona Backup for MongoDB remains compatible with MongoDB 4.4 and Percona Server for MongoDB 4.4; however, further enhancements and bug fixes are no longer tested against this version. -
Packaging Changes
Percona Backup for MongoDB is available on Ubuntu 24.04 (Noble Numbat).
Percona Backup for MongoDB is no longer supported for Ubuntu 18.04 (Bionic Beaver), Debian 10 and Red Hat Enterprise 7 and derivatives as these operating systems reached End-Of-Life.
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.6.0.html
Join Percona Squad
Participate in monthly SWAG raffles, get an early access to new product features and invite-only “ask me anything” sessions with database performance experts. Interested? Fill in the form at https://squad.percona.com/mongodb
Contact Us
on Forums
by Email
or Professional Support
v2.5.0
Release Highlights
- You can now restore the desired subset of custom databases with users and roles created in them. This is useful for deployments where each user has an individual database and authenticates against it.
- Previous versions of PBM required that readConcern and writeConcern are set to majority in MongoDB. You can now explicitly override this behavior, and thus, ensure backups in clusters configured to operate without the majority or lost it for some reason.
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.5.0.html
Contact Us
on Forums
by Email
or Professional Support
v2.4.1
Release Highlights
This release fixes the issue with failing incremental backups. It was caused by the backup metadata document reaching the maximum size limit of 16MB. The issue is fixed by introducing the new approach of handling the metadatada document: it no longer contains the list of backup files which is now stored separately on the storage and is read by PBM on demand. The new metadata handling approach applies to physical, incremental and shapshot-based backups.
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.4.1.html
Contact Us
on Forums
by Email
or Professional Support
v2.4.0
Release Highlights
- You can now delete backup snapshots of a specific type. For example, delete only logical backups which you might have created and no longer need. You can also check what exactly will be deleted with the new
--dry-run flag. This improvement helps you better meet the organization's backup policy and improves your experience with cleaning up outdated data. - Point-in-time recovery oplog slicing is now running in parallel with backup snapshots. This ensures that you can make a point-in-time recovery to any timestamp from very large backups that take hours to make.
- Percona Backup for MongoDB packages are now also available for ARM64 architectures. Thus, users can not only run Percona Backup for MongoDB in Docker containers on ARM-based workstations but also install the packages on those workstations. The ARM64 packages are available for the following operating systems:
- Ubuntu 20.04 (Focal Fossa)
- Ubuntu 22.04 (Jammy Jellyfish)
- Red Hat Enterprise Linux 8 and compatible derivatives
- Red Hat Enterprise Linux 9 and compatible derivatives
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.4.0.html
Contact Us
on Forums
by Email
or Professional Support
v2.3.1
Release Highlights
- Added support for Percona Server for MongoDB 7.0
- The ability to define custom endpoints when using Microsoft Azure Blob Storage for backups
- Improved PBM Docker image to allow making physical backups with the shared mongodb data volume
- Updated Golang libraries that include fixes for the security vulnerability CVE-2023-39325
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.3.1.html
Contact Us
on Forums
by Email
or Professional Support
v2.3.0
Release Highlights
- 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.
- The ability to view the backup contents improves troubleshooting of backups in environments where databases are often created and / or dropped.
- The ability to make 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.
- Improved validation of a base backup snapshot for point-in-time recovery aligns the recovery flow for logical and physical backups.
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.3.0.html
Contact Us
on Forums
by Email
or Professional Support
v2.2.1
Release Highlights
With this release you can increase the wait time for backup to start, thus eliminating the PBM failure when creating $backupCursor takes longer than usual.
For more details, please check out the full list of improvements:
https://docs.percona.com/percona-backup-mongodb/release-notes/2.2.1.html
Contact Us
on Forums
by Email
or Professional Support
