it would be great when the content of roundcubemail, like contacts and identities can be included in the backup. It would make life easier in case of restoring a customer who uses only the webmail feature for mail.

I mounted a remote server via sshfs and set it as the plesk backup repository, so I can backup my domains through sftp (with a keyfile).

But now, whenever I try to upgrade my plesk installation, plesk writes files to my backup repository (i.e. mysql backup before a mysql upgrade) and immediately tries to change the owner of the file, which fails because chown it is not supported on mounted directories.

The best solution would be to provide the option to set a different path for automated backups.

Enable additional Schedule Backup and provide an option to disable the obligation to make a Full Backup (letting user the option to create additional Incremental Backups, without messing things like repeated Full Backups). This already happends if the Admin and Client both setup Backups, it create multiple Full Backups which is not necessary since Admin Backups are create in behalf user.

Please add differential backups.

Exclude mailing lists from incremental backups

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.

Please enter the percentage of database restore in progress ... it is very frustrating to restore without knowing either the time left or the totality of kbytes transferred and remaining, with progress a bar
Thank you

possibility to backup single subdomains

Hello, I would like to be able to download the files to my documents to be able to modify the code etc.

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

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.

Would love to see Rsync support added. SFTP is slow.

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 -

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.