2.4.0

• Added ability to delete backup snapshots of a specific type. For example, delete only logical backups which you might have created and no longer need.

• Ability to check what exactly will be deleted with the new --dry-run flag.

• Point-in-time recovery oplog slicing is now running in parallel with backup snapshots. This ensures 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 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

2.3.1

• 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.

2.3.0

• 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.

2.2.1

• Configurable wait time for PBM to start a physical backup

2.2.0

• Point-in-time recovery from physical backups is now automated similar to point-in-time recovery from logical ones. This offloads your DBAs on performing manual oplog replay on top of physical restore, ensures data consistency and unifies the user experience with PBM.
• Owners of large data sets can now use PBM to create external physical backups as EBS snapshots or via a technology of their choice and restore from those backups with the data consistency guaranteed by PBM. Thereby they benefit from increased performance and reduced downtime, and are sure that their data remains consistent. This is the technical preview feature.
• The ability to restore from physical and incremental backups to a new environment with different replica set names extends the set of compatible environments for physical restore.

2.1.0

• Incremental physical backups are GA. Backups made with previous PBM versions are incompatible for restore with PBM 2.1.0
• Support of sharded collections for selective backups and restores. Sharded timeseries collections are not supported
• Support of parallel download of data from S3 compatible storage for physical restore
• pbm cleanup command to delete old backups and PITR chunks for a defined time period.
• Improved physical restore of data encrypted at rest: now master key rotation using the same key is possible for Vault.
• Support of AWS tokens for S3 storage access.

2.0.5

• Fix for physical restore for backups having taling slash in dbpath
• Fix for CVE-2022-41723

2.0.4

• Ability to define the custom path to mongod binaries for physical restore
• Fixed physical restore into a new environment

2023-01-11

• Incremental backups (tech preview)
• Sharding support for selective backups and restores
• AWS IRSA support
• Support of RHEL9

2.0.2

• Error messages in JSON format for pbm status output
• Fix for CVE-2022-32149