Issues

PBM unable to start backup due to 'context deadline exceeded' error

Add support for SSE-S3 for S3 providers

Block logical restore of sharded timeseries collections

Release notes 2.6.0

Leftover backup lock after successful physical restore

pbm profile add should fail if pbm-agents doesn't have permissions to specified storage

Impossible to start PITR in case there are old oplogs on the storage

Occasionally pbm-agent is locked out of starting the slicer

Physical restore fails with "there was an index build in progress"

Physical backup is not completely removed from the storage after executing pbm delete-backup or pbm cleanup

Filesystem storage writes should write, fsync and rename

PITR generation does not resume following agent restart during backup

Reporting actual priority with pbm status

"node in not suitable for restore" message is confusing

The backup cannot be taken from the primary node if even it has the highest priority in PBM

uploadPartSize, maxUploadParts not printed in log

Hardcoded timeout for resync and delete operations in PBM cli code

Node Priority Control in the Oplog Slicing

Multiple storage configuration for backups

logical PBM issue archive parser: corruption found in archive; ParserConsumer.BodyBSON()

Support multiple storages

PBM SDK: list agent statuses

Backup hangs after pbm-agent is restarted

When installed PBM, pbm-agent URI is setting different as compared to the doc

Take node priority into account for oplog slicing

pbm pitr.oplogOnly backup set the priority

Show nodes priorities

PITR slicing eventually could end up on primary node

invalid remote store url in text output when starting backup