All work

PBM Physical Restore Randomly Fails During clean-up and reset replicaset config Stage

PBM reissues the previously executed command

There's no straightforward way to retry physical restore if one of the pbm-agent processes fail

Restore status is stuck running if one of the pbm-agent processes fail

SPIKE: PoC for Controll Collection RS

Redesign Remote storage configuration for PBM

Provide clarification for replica set name mapping

Add new column showing the backup "Status" to pbm status output

Backup has indefinitely running state if failed on `errGetObj Err: NoSuchKey: The specified key does not exist.`

PBM fails to catch up PITR if `oplogOnly` option is enabled

Option to exclude in-memory nodes from backups in a sharded cluster

PBM status returns error if pbm --force-resync and --file are called together

pbm cannot connect to db due to invalid PBM_MONGODB_URI with requireTLS

Backup is marked as successful despite oplog wasn't uploaded

Enable PBM to monitor storage changes and automatically update metadata in the PBM system collection

Restore backup from replica set to a sharded cluster

PBM backup is not starting for 40 shard cluster.

Log information about throughput and %progress

Improve 'Point-in-time restore from physical backups' section

Latest PBM (2.9.1) tar package is empty

Expiring Kerberos Ticket requires automatic renewal

PBM doesn't return a clear error if backup can't be started in mixed env

Custom S3 TLS Certificate support in PBM

Possibly incorrect namespaces exclude

Users restored incorrectly in selective restore

PITR selective restore does not restore users

Missing PBM 2.9.0 in compatibility matrix

PBM logs inexistent PITR error during physical restore

Document that priorities cannot be set using "config --set"

Improve resync performance

Add configurable timeout for pbm backup

PBM unable to take physical backup in mixed deployments

Configuration for Fallback dbpath feature

Allow pbm-agent to run with no database connection

Oplog collection stops without any apparent reason

Remove any db queries during physical restore

Fallback dbpath for physical restore

GCS support concurrent downloading of the single file

Remove the copy of users and roles during logical backup

Add PBM support for Workload Identity Authentication

pbm describe-restore returns empty output if a profile used in config file

pbm profile sync fails

Restore from pbm hangs after some time.

Document PBM SDK

Unformatted error in restore metadata

HMAC support for GCS

Ability to set a timeout duration for stopping the balancer

Wrong s3 URI in pbm status

Sharded cluster restoration failure in 2.8.0