Issues

Check AWS credentials while adding s3 storage for backup

Add ability to restore a logical bkp for a mongo sharded cluster

Add a way to ignore insecure certificates when adding a backup destination

Backup Scheduling - misleading "Incremental" label

Basic Backup Alerting

Improve filter functionality on the Backup pages

MongoDB Backup - Can't set oplog span duration

MongoDB Backup - Can't set priority

PITR on top of MongoDB physical

Scheduled Backup Creation - Confusing "backup type" selection

Backup Table in PMM - Important information missing

Backup Table in PMM - Allow grouping by cluster

Separate PITR retention for MongoDB backups

It cannot be restored with the changed datadir

MongoDB Backups: Monitoring and Alerting - Phase 2

Add possibility to delete/terminate backup which is stuck

[FE] Add filtering options to the Backup pages similar to Inventory

Allow multiple backups to be selected for deletion

create backup internal server error

Incremental MongoDB Backups

MongoDB Backup / Service Name - Make the text search case insensitive

MongoDB Backups: Basic Monitoring and Alerting

(DOC) Backup management tooltip opens non-existed page

Schedule backup for a Mongo cluster, not a specific service/node

[DOC] Backup Management : restore on a new replica set cluster

[FE] Backup Management : restore on a new replica set cluster

BM folder field has a inconsistent validation on BE & FE

Lack of information about mongod required to be in the PATH for backups

Insufficient information in the backup error log message when binary not found

Typo in Point-In-Time Recovery error message for sharded cluster feature

Implement Differential Backup Feature For MySQL/PostgreSQL/MongoDB

Qpress/quicklz is deprecated in PXB 8.0.31-24

Errors from cli are not being propagated to UI on switching PBM PITR status.

BM: Unrestricted Special Characters Accepted in Folder Property

Folder path not properly rendered in Backup Management feature of PMM2 for very long folder locations

unauthorized backups are possible through a directory traversal attack in the Backup Management feature

If user specified directory doesent have proper permissions the error is visible only in via pbm tool and does not reflect on UI via display log feature

Empty logs in PMM UI when PBM authentication fails

MongoDB backups don't work if authentication mechanism other than SCRAM is used

DBaaS: It's possible to delete used location

[Backup Management] Consider implementing removing and retention policy for artifacts on local storages

Wrong name for Backup inventory

Inconsistent subcategories

Interoperability PBM CLI <--> PMM Backups

Running separate schedule jobs at the same time does not produce artifacts

New config isn't being implemented to pbm when trying to restore not the latest backup

MySQL system service cannot be found in some cases

Backup Management - enabled by default

Scheduled backup tasks not starting properly