Percona Backup for MongoDB 2.17.0 (2026-10-14)¶

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.

PBM 2.17.0 improves physical point-in-time recovery (PITR) and restores of time series collections. It also helps you identify why an incremental backup failed and delete backups left in an unfinished state.

Release highlights¶

Physical point-in-time recovery restores index changes¶

Physical PITR now applies index creation, deletion, and modification operations from the oplog. Previously, PBM skipped them. The restored database now has the same indexes as the source at the restore target time.

Physical restores, with or without PITR, are also more stable. PBM now disables the time-to-live (TTL) monitor for the duration of the restore, so TTL deletions no longer interfere with oplog replay or cause duplicate key errors in collections with unique indexes. TTL monitoring resumes by default when you start MongoDB after the restore.

This release also fixes a storage download deadlock that could leave physical PITR waiting indefinitely. Oplog replay no longer blocks the reads PBM uses to track restore progress.

For details, see Restore to a point in time from a physical backup.

Time series collections restore without errors¶

PBM fixes two issues that could interrupt restores of time series collections:

Index creation during PITR no longer fails with IllegalOperation errors.
Logical restores, including PITR, no longer fail with DocumentValidationFailure errors when the time series collections were backed up under high write throughput. PBM now bypasses document validation during oplog replay.

For additional details, refer to the Restore time series collections documentation.

Improved error reporting for incremental backups¶

When an incremental backup fails on a shard, PBM reports the underlying error instead of a generic convergence timeout. The message helps you identify the cause and decide what to do next.

For example, if the previous incremental backup was made on another node, PBM explains that the incremental backup history is unavailable and that you need to create a new base incremental backup.

Changelog¶

Improvements¶

PBM-1775: PBM now reports the failing shard’s error for backups in sharded clusters, including missing incremental backup history, instead of a generic convergence timeout.
PBM-1821: Updated Go to 1.27.1, along with the MongoDB Go driver, MongoDB Database Tools, and other third-party dependencies.

Fixed bugs¶

PBM-1762: Corrected index creation during PITR of time series collections to prevent IllegalOperation errors.
PBM-1763: Prevented DocumentValidationFailure errors during oplog replay for time series collections. For collections with expireAfterSeconds, manually disable the TTL monitor before a logical restore, including PITR. Keep it disabled throughout the restore. Restore its original setting afterward, even if the restore fails.
PBM-1779: PBM now automatically disables the TTL monitor during physical restores, with or without PITR. This prevents TTL deletions from causing duplicate key errors during oplog replay.
PBM-1795: Eliminated a storage download deadlock that could prevent physical PITR from completing.
PBM-1802: Backups with stale heartbeats can now be deleted, even if their metadata shows a starting or running state.
PBM-1813: Fixed logical restore failures caused by bucket data validation errors in time series collections backed up under high write throughput.
PBM-1817: Corrected physical PITR to apply index creation and deletion commands from the oplog, as well as index changes made with collMod.
PBM-1817: Corrected physical PITR to apply index creation and deletion commands from the oplog, as well as index changes made with collMod.

Last update: October 15, 2026
Created: October 4, 2026