Plesk does not rotate backup logs and we needs to delete them by manual.
Backup log might be very big, therefore Plesk should rotate backup logs automatically to prevent oppression of disc capacity by increasing backup logs.

Related KB: http://kb.odin.com/en/113748/

Include Mysql events in Plesk backups.

Currently backups created via Bacup manager or via
plesk db backup command, do not include mysql events.

Plesk Migrator is a great tool but it don't migrate backup settings.
Please make this possible !

Hello, is it possible to add Pcloud backup app to plesk like other services amazon cloud or dropbox.

Include in Plesk a new feature to find out which Plesk login has created or restored a backup in Plesk. This could be done recording such logs in Plesk Action Log.

Would be nice to have the option to choose other compression formats for backups, especially bzip2 or xz. To reduce compression time, parallel implementations can be used (pbzip2 and pxz). Additionally there should be an option to set compression level (1-9).

possibility to backup single subdomains

May it could be great for a next release of Plesk, that comments could be display in the backups list from the start! Correctly comments for backups on the remote FTP server can not be viewed.

Hello ,

Can you please add in:
Home
Tools & Settings
Event Manager
Adding Event Handler >>Event

options for backup ? Like backup created , updated and etc ?

Thanks

In database Tab add new feature. Scheduled mysql daily and export to private folder.

Is is extra backup, not replace the original BackUp system of all data.

There is no option to encrypt backups. I do not trust Google or any other cloud service. Yet I could use the (otherwise completely useless) storage to put my backups there.

So please include a proper and secure encryption. Thanks!

Edit:
It could be as easy as running gpg as a last step before uploading:

Encrypting (simple tar example):
tar -czf - [FOLDERS] | gpg -c --batch --passphrase [PASSWORD] -o backup.tgz.gpg

Decrypting:
gpg -d --batch --passphrase [PASSWORD] backup.tgz.gpg | tar -xzf -

Plesk does currently only support Amazon S3. Amazon Glacier is cheaper than S3 and also good for backups. Also support for Google Cloud would be great since at the moment, Plesk does only support Google Drive which is no professional backup (example: https://github.com/plesk/ext-cloud-backup-example).

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.

Please, add a feature to be able to check Backup manager settings (including Scheduled backup settings), server-wide and for the particular domain via CLI. It would be very convenient for server administration to get information about backup settings in one place: for example, if there are multiple domains with different settings.

Allow excluding patterns from full backups with more control.
For example, exclude pattern A only from Reseller Accounts and pattern B only from Costumers, etc.

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.