It is required to make possible to list backups via REST API.

Hello,

Please add option to restore original file timestamps in backup restoration in Plesk.

Currently, it can be acveived only manyally using tar utility:

tar -xvzf /var/lib/psa/dumps/domains/example.com/backupuser-data1902060958.tgz

When a customer in Plesk removes a subscription-level backup which is a part of full-server backup (or reseller's backup and some customer's backup in case of special rights), it is not displayed anymore in subscription's backup manager. However, it is not actually removed from the server. This confuses customers because they are not aware of what actually occupies so much disk space.

Feature suggestion: make some note/banner in customer's backup manager to inform them that there are some backups which were created on a higher level.
Or
Prevent backup deletion if created at an higher level.

Add possibility to Plesk service plans to restrict the ability for a customer to create incremental backups so that a customer has a permission to create full backups only.

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.

It would be useful to be able to remove from a server-wide backup only particular domain's data (such as mailbox accounts) as it will help to manage server's disk space in a more efficient way and store only needed data

Add a possibility to store backups on Linode Object Storage. As it is done for DigitalOcean Spaces, Amazon S3 Backup, Google Drive Backup

Currently, restored backups, which have been downloaded from a remote storage, are being stored locally and appear in the backups list and become part of a backup process.
Expected behavior:
Download, restore & delete downloaded backup files. Remove from the backup list.

Add to Plesk functionality to allow the clients to restore the backups on the remote server via FTPS.
The administrator can create backups and clients can restore their own parts of backups. As how it is done with common backups on local storage

If you do not want to use FTP or SFTP you can also use Samba

I'd really like to have a UI to select what is contained in a serverwide scheduled backup.
We have a couple of domains where people dump photos and videos for further processing, amounting to 100s of GBs, and we don't need backups of those.
The UI you got for the restore dialog would be just fine.
I think it makes more sense to select what is contained, than what to exclude.

It is required to create/restore SFTP backups via CLI to automate the process

The Backup Manager should be able to show the backups of all domains below the admin, including resellers.

Have a better backup system (Can select exactly what files you want to backup in a good UI)

Since I installed the "Plesk mobile" extension, my daily server backup via Plesk (only configuration and e-mails) is much larger than before and gets larger every day! There is a log file called "MobileConnector.log" in that backup and this file currently is 150 MB in size (it increases by about 50 MB per month).

I would like to have an option to exclude this file. As it's part of an extension, this log file cannot be excluded via the checkbox "Exclude logfiles"! This option is not even visible, because I do not backup user files.

It's a nuisance having to go back to the main page to do a backup after uploading new or revised files.

Add the possibility to check the content of a backup so it can be reviewed and identify if the backup contains the needed files / information such as by date, name, etc.

Please availlable export backup button in mssql databases like phpMyAdmin.

Unfortunately, it's not possible to download backup files via applications such as internet download manager now, and this can be the reason of some problems for users (Failing downloads and repeating them) and hosts (ٌWasting bandwidth and other resources of servers).

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