Skip to content
Percona Software for MongoDB Documentation

Percona Backup for MongoDB 2.7.0 (2024-10-09)

Installation

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 primarily focuses on code stability and bug fixing. However, it also provides the following improvement:

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

Improvements

  • PBM-1312, PBM-1362, PBM-1400 - Allow changing logical backup concurrency

  • PBM-1351 - Allow PBM running in Amazon Elastic Kubernetes Service (EKS) to access AWS services using the credentials from AWS default stack (Thank you Alexey Torkhov for contribution).

  • PBM-1397 - Add file checks for physical and incremental backups

Bugs Fixed

  • PBM-397 - Fixed the issue when multiple pbm-agents run for the same mongod process by checking and logging unexpected heartbeat updates.

  • PBM-823 - Fixed the issue with files not being deleted from storage after cancelling backup.

  • PBM-886 - Fixed data race during point-in-time recovery upload cancellation

  • PBM-921 - Fixed the issue with failing point-in-time restore on view restore stage by ensuring the system.views collection exists before restoring a view or timeseries collections. (Thank you Asel Magzhanova for reporting this issue)

  • PBM-1114 - Check backup files before marking a logical backup as done to ensure it can be restored from

  • PBM-1229 - Fixed the issue with external backup failing to finish (Thank you Julien Riou for reporting the issue)

  • PBM-1296 - Fixed the issue with PBM failing during point-in-time restore when a timeseries collection was created during oplog slicing by reusing the auto-generated UUID for that collection for view creation.

  • PBM-1297 - Fixed the issue with point-in-time restore failing if config.databases collection is created during oplog slicing by allowing this collection to be created during oplog replay stage

  • PBM-1316 - Prevent running pbm cleanup when a backup is in progress

  • PBM-1338 - Add the start and finish time for the describe-restore command output

  • PBM-1356 - Fixed the issue with failing pbm commands by starting logging later after the collection is created

  • PBM-1369 - Fixed the issue with a stuck logical backup when a pbm-agent is lost after the dumpDone stage.

  • PBM-1382 - Fixed the priority display for delayed nodes in pbm status output

  • PBM-1387 - Fixed the issue with not showing default values for config options

  • PBM-1391 - Fixed the issue with the Percona Server for MongoDB crashing after enabling point-in-time recovery routine after physical restore

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.

Community Forum Get a Percona Expert

Last update: October 9, 2024
Created: October 9, 2024