Skip to content
Percona Software for MongoDB Documentation

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

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Backup for MongoDB 2.13.0 (2026-03-03)

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

Secure backups in Google Cloud Storage (GCS) with Workload Identity Federation (WIF)

Percona Backup for MongoDB (PBM) 2.13.0 now supports Workload Identity Federation (WIF) when authenticating with Google Cloud Storage (GCS).

With WIF, you can upload backups to GCS without relying on long-lived service account JSON keys. PBM authenticates using short-lived tokens obtained through federation with an external identity provider (IdP).

Workload Identity Federation lets on-premises or multicloud workloads access Google Cloud resources using federated identities instead of a service account key, eliminating the maintenance and security burden of service account keys.

For detailed information, refer to our comprehensive documentation.

Selective backups including users and roles

Percona Backup for MongoDB already supports selective backups of databases and collections. Now, the selective backup can also include users and roles defined within the database. This ensures that access control is restored along with the data.

To back up a specific namespace and include users and roles:

pbm backup --ns="mydb.*" --with-users-and-roles

For detailed information about this feature, see our documentation.

Changelog

New features

  • PBM-1660: Percona Backup for MongoDB (PBM) 2.13.0 now supports Workload Identity Federation (WIF) for authenticating with Google Cloud Storage (GCS).

  • PBM-1294: Percona Backup for MongoDB already supports selective backups of databases and collections. Now, the selective backup can also include users and roles defined within the database.

Improvements

  • PBM-1438: Added indexes across all PBM collections to improve query efficiency and reduce response times when accessing pbmLog data. This enhancement ensures faster log retrieval and smoother performance during backup and restore operations, particularly in environments with large datasets or frequent queries.

  • PBM-1521: You can now restore the desired database to a specific point in time, including all associated users and roles. This enhancement ensures that both data and access configurations are consistently recovered.

  • PBM-1563: Added support for treating MongoDB error code 50917 (oplog rollover during backup cursor establishment) as a retryable error during physical backups. This aligns with the existing handling of error code 50915 (checkpoint conflict) and improves backup reliability by automatically retrying when transient oplog rollover issues occur.

  • PBM-1645: PBM now triggers a storage re-sync only when the storage identity/connection parameters change. Updates to storage settings that don’t affect how PBM connects to the backend no longer force a re-sync, reducing unnecessary load and avoiding unnecessary delays during configuration changes.

  • PBM-1649: The pbm cleanup command now supports targeting a specific storage profile via a new --profile flag. You can run pbm cleanup --older-than=<TIMESTAMP> --profile=<profile_name> to clean up backups on the selected profile. If --profile is omitted, PBM preserves the existing behavior and performs cleanup using the main profile for full backward compatibility.

  • PBM-1663: Enhanced the pbm status and pbm list commands to display the Profile (storage) associated with each backup, making it easier to identify where backups are located. A new option has also been added to filter results by a specific Profile, showing only backups for the chosen storage.

  • PBM-1665: Point-in-time recovery (PITR) now continues uninterrupted when logical backups are performed using external storage profiles. The backup process on external storage no longer interrupts oplog slicing on the main storage. PBM saves oplog chunks for such backups on both the main and external storage, ensuring consistent PITR coverage.

  • PBM-1673: Improved restore output by clarifying oplog replay messages, making progress and restore state easier to interpret.

  • PBM-1690: Percona Backup for MongoDB now supports restarting pbm-agent only at the copyReady step during external (snapshot-based) restores. At this stage, mongod is stopped, and the data directory has been cleared, so nodes remain on hold, awaiting new snapshot data files provided via an external mechanism (for example, snapshot restore or rsync).

Fixed bugs

  • PBM-1488: Fixed an issue where Point-in-Time Recovery (PITR) would stop saving oplog slices if a failure occurred during the oplog copy process from a backup.

  • PBM-1561: Selective logical restores in sharded clusters now work correctly when the target database or collection already exists. PBM no longer fails due to pre-existing namespaces. During cleanup, it drops only the namespaces specified with --ns using _shardsvrDropCollection for --ns "db.coll" and _shardsvrDropDatabase for --ns "db.*". The same fix applies to PITR restores (--time).

  • PBM-1614: Resolved issues with backup metadata serialization and error handling. PBM now reliably encodes/decodes and persists metadata in external storage using a value type (avoiding nil-pointer cases), provides more descriptive errors across backup workflows, and includes new MinIO-based tests to validate metadata serialization round-trips.

  • PBM-1691: Resolved an issue where the PBM CLI exposed SSE credentials in JSON output.

Last update: March 3, 2026
Created: March 3, 2026