Skip to content
Percona Software for MongoDB Documentation

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

For help, click the link below to get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Backup for MongoDB 2.15.0 (2026-06-17)

Installation

Percona Backup for MongoDB (PBM) is a distributed, low-impact solution for creating consistent backups of MongoDB sharded clusters and replica sets, and restoring them to a specific point in time.

Release highlights

Oracle Cloud Infrastructure support

PBM now supports Oracle Cloud Infrastructure (OCI) Object Storage as a remote backup destination through a dedicated OCI-native driver. This integration enables seamless backup and restore operations across OCI environments.

Authentication methods

PBM supports multiple authentication mechanisms for OCI Object Storage, including Workload Identity authentication. This approach allows secure access to OCI resources without requiring API signing keys, reducing operational overhead and strengthening security.

Supported authentication methods:

  • Choose User Principal when PBM runs on premises, on OCI, or in other cloud environments.
  • Choose Instance Principal when PBM runs on OCI Compute instances.
  • Choose OKE Workload Identity when PBM runs in Oracle Kubernetes Engine (OKE) enhanced clusters.

Benefits

  • Secure access with OCI-native identity integration

  • Reduced operational overhead by eliminating manual credential management

  • Deployment flexibility across on-premises, cloud, and Kubernetes environments

For detailed information on OCI, refer to our comprehensive documentation.

Software Bills of Materials (SBOMs)

Percona Backup for MongoDB (PBM) now provides Software Bills of Materials (SBOMs). SBOMs improve transparency in the software supply chain by documenting the components and dependencies in a build. They are generated automatically as part of the release pipeline in the industry-standard CycloneDX 1.6 format.

SBOMs are distributed through the following channels:

  • GitHub: The latest SBOM is placed in the root of the percona/percona-backup-mongodb main branch.

  • Binaries/Tarballs: An SBOM file is included in the root directory of the release archive.

  • Packages: For .deb and .rpm packages, the SBOM file is installed in a standard documentation directory such as /usr/share/doc/percona-backup-mongodb/.

  • Docker: The SBOM is attached directly to the Docker image as metadata.

If you want to dig deeper into this topic, refer to our documentation.

Changelog

New features

  • PBM-1727: Percona Backup for MongoDB (PBM) now supports OCI Object Storage as a remote backup destination through a dedicated OCI-native driver.
  • PBM-1728: Percona Backup for MongoDB (PBM) now supports multiple authentication methods for Oracle Cloud Infrastructure (OCI) Object Storage, including Workload Identity.
  • PBM-1710: Percona Backup for MongoDB (PBM) now provides Software Bills of Materials (SBOMs) for every release.

Improvements

  • PBM-1370: Agent logs now include the reference date or interval supplied to cleanup commands. Previously, only the command receipt and epoch timestamp were recorded, making it difficult to determine which cleanup criteria were applied during troubleshooting and audit investigations.
  • PBM-1668: The restore command now accepts a commitQuorum option that controls when the primary commits an index during a restore operation. You can set this to majority, votingMembers, or a specific number of nodes. Without this option, MongoDB defaults to votingMembers, which requires all data-bearing voting members to complete index building before the index is committed. In large replica sets, this can significantly delay restore operations if index creation is slow on even a subset of nodes.
  • PBM-1715: Physical backups and restores now support a numParallelFiles option that controls how many files PBM copies simultaneously during a backup operation. Increasing this value can improve backup performance on systems with high disk throughput.
  • PBM-1754: PBM now allows configuring the buffer size used during physical backup and restore operations. This enhancement provides greater flexibility for tuning memory usage and data transfer performance, enabling you to optimize backup and restore throughput based on your environment and workload requirements.

Fixed bugs

  • PBM-1687: Fixed an issue where point-in-time recovery (PITR) was blocked when two backup commands were executed simultaneously.
Last update: June 17, 2026
Created: June 12, 2026