At this moment, you can set only 1 rule to make backups (daily, weekly, or monthly). My idea is to make multiple backup rules (ex. which daily backups should be deleted) or simply make more backup options.

Ex:
I want to make daily backup and delete every older than 2 days, except one day of the week and one day of the month.

ex interface:
Make [daily/weekly/monthly] backup and keep only:
[n] daily backups (enabled only for daily backups)
[n] weekly backups (enabled for daily and weekly backups)
[n] monthly backups (enabled for daily, weekly and monthly backups)

So, if someone picks daily backups from 2 days, but also wants a 1 monthly backup, the script makes daily backups and deletes every backup older than 2 days except 1 monthly backup. This way it doesn't make double work - backup for daily backups and backup for monthly backups.

Hey guys,

I am sure that I speak for hundreds of users when I say that having a limit on backups per customers and or subscriptions should be an important and available option. The option to also limit backups based on the customers subscription storage size will be even better. Otherwise, customers who overuse the backup option will dramatically increase storage space on the server without realization of the administrator. It wouldn't be ideal for an administrator to enter the dumps folder to delete random customer backups. Really hope you guys can resolve this and add this feature as soon as possible.

This may also be a security issue.
Currently there are no special protection of user content in the backup. Plesk protects only its sensitive data, web content archived without any encryption.

If some gains ADMIN access to a wordpress/drupal/other web applications install parts of the Plesk container file system, cron jobs, etc will be compromised and would undoubtably increase exponentially the chances of the system to be exploited with virus, rootkits, malware “indirectly” affecting Plesk. (as an analogy no point to build a metal wall if the door is still glass)

So, in other words ... if a wordpress installation is compromised the installations of malicious (or not) plugins can lead to the installations of rootkit, malware and virus at the container. I cannot see for a second how this would be good for any Virtuozzo container running Plesk and how you could consider Plesk not being affect if for instance the container is used to conduct a DDOS to a random host.

Initial Thread
http://forum.odin.com/threads/plesk-12-x-x-backup-manager-encryption-security-issue.334691/#post-786917

It would be great to have a single interface to manage backups of individual accounts (single-domain or single user).
I would like to manage a single server backup ftp and let me choose which accounts to backup.

Obviously the backup file must be "single" for each account and not a single file for the entire server. If you want to make the restore of a single account, I have to use a single backup file.

Currently I have a script that through bash (or cygwin for windows) backs up the single account by bees and upload via ftp on external storage. I would avoid using external tools and remain in plesk.

I've seen many options for backups, but it would be a great addition if we could use the backup schedule to make a backup local AND somewhere remote.

Now i can schedule backups either only local or only remote and since i cannot make multiple schedules for remote backups and local backups i have to make local backups with the scheduler and do things by hand to get another backup in my personal FTP storage.

I prefer to have backups local, for quick restore availability and remote for when sh*t hits the fan.

So, i'd like to see an option to either run multiple schedulers so you can run two, one to backup local and one to backup remote, or an option to make a backup local and automatically upload it to my personal share.