Issues

PBM logs inexistent PITR error during physical restore

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

Backup Container Crash During Restore

Restore with PITR from a Different Cluster

Backup and PITR Chunk Deletion Behavior

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

Avoid exposing db credentials in /etc/sysconfig/pbm-agent

Configuration profiles are not shown in status

Physical backup with files that have reached remote storage limits

Integrate PBM with cloud provider snapshot technology

PITR will stop saving the oplog if the process of copying the oplog from the backup fails

Queryable backup and restore for PBM

pbm-agent.init file has misspelled group name and it fails to start the pbm agent

Allow/ignore "Z" marker in the restore timestamps

PBM cannot restore/resync from a read-only datastore, improve to allow this to work even if some restrictions

PBM fails to restore when collections present that have a required partialFilterExpression due to unique index

PBM won't work by default on server with single CPU

Update the Get Help widget and add Get help page

Add tests for S3 & GCP storage access

Swap AWS s3 v1 -> v2 SDK API

Extra slash symbol in bucket/prefix options breaks PBM ability to save or discover backups on storage

Migrate to AWS SDK for GO v2 and GCP SDK

SPIKE - Physical restore assumes a functioning cluster

Remove kingpin dependency from pbm cli

Selective backup/restore for sharded collections fails for setups with config shards

Fix backup type in "another operation in progress" error message

pbm backup names - custom name / without special chars

Increase test coverage for oplog restore

Configuration file for all pbm-agent's options

Stop balancer and chunks autosplit automatically during restore