Keep Static Back up, that can be deleted ONLY manual. Prevent rotation to delete a specific back up that i decice, so i have a base back up as reference for as long as i need. That will make me feel safe that if the 7 days of rotation that i have to my back up, passed, i still be able to retrive a back up!

It should be possible to specify files to be excluded from manual backups globally

Add capability to select the region when creating S3 Buckets using root account credentials

I tried to change this by modifying extension files but all the files are encrypted.

Backup / Restore manager is fine, but what if we only want to restore one / several tables, not the whole Database?
Add feature to restore single tables only.

Or even more flexible: add the possibility to restore a DB dump to a file. This file can then be searched / adjusted to restore specific tables only. Once it is adjusted we could load it in the DB / perform the restore.

At the moment the extension order of Plesk multi-volume backups is the following:
<DateFormateHHMMss.zip>
<DateFormateHHMMss.zip1>
<DateFormateHHMMss.zip2>

This means that volumes .zip1, .zip2 can not be extracted after their downloading because they have an incorrect zip extension format.

The idea to change the extension order of Plesk multi-volume backups to:
<DateFormateHHMMss>.Zip
<DateFormateHHMMss>1.Zip
<DateFormateHHMMss>2.Zip

That the multi-volume backups have the correct zip format and can be extracted.

I suggest adding functionality to restore a domain or subscription from a server-wide backup on the Plesk server, where this domain or subscription is missing (for example, it was deleted before). This is very inconvenient when you have to create a nonexistent subscription, then restore it, and then separately restore the domain in it.

When you want to Restore a Backup from FTP, first this backup it's downloaded to the Local Plesk Server and then the restoration starts.

At the end of the restoration process, the Local Backup it's still there, maybe it's better to save this space deleting this Local Backup and maintain only the FTP backup which was downloaded.

Backup task may increase server load. In order to balance it, it is required understand how long task has been running.
Currently it is possible to check only from log files, which is not very convenient. Please, add ability to simply check this info in Plesk UI.

move the remove database button to somewhere else, could accidently remove a database when trying to export.

Restoring a backup in Tools & Settings > Backup Manager always results in a generic message:

Restoration of the backup <timestamp> completed

But this message remains the same both after restoring a full server backup or just some specific domains, which can be confusing.

If only specific domains have been restored, please add a separate message listing these domains.

It'll be useful to have the ability to configure the retention period of the backup. Right now it's only possible to set the "Maximum number of full backup files to store (including both scheduled and manual backups)".

While it'll be useful to set something like "Keep backup for "x" weeks", to have more flexibility, when it gets to the backup storage.

Create an extractor when restoring a partial backup that could only download what is needed from the external backup in order to save bandwidth and space on disk and time

Hello,

Would be a good UX/UI improvement to get informed that ALL databases of all domains under the subscription would be restored in case the subscription restored from the backup. (all configuration and content)

Exporting a backup via "pmm-ras" utility may bring down the server because it ran out of disk space during the procedure:

plesk sbin pmm-ras --export-dump-as-file --dump-specification=backupinfo<timestamp>.xml --dump-file-specification=/root/backup.tar

Please improve the "pmm-ras" utility to check for free disk space before starting the operation to avoid these scenarios

It would be nice to have an option which allows to update the subscription's backup settings(exclude files/logs) via CLI.

There are so many notifications in backup manager regarding failed backups and clearing them 'close this message' is so slow. It would be nice to have a way to clear them all at once

Add some CPU/IO % limits for backups to avoid consuming all resources from the server

Currently, Plesk backup manager creates incremental parts only for the web and mail content. And Plesk extensions backup always contain full data even if there were no changes. It is required to add incremental backups for Plesk extensions