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.

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.

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.

Currently it seems the backup priority only takes CPU into account and not I/O

I would prefer the backup low priority settings to be changed into specific values. For example

CPU PRIORITY -> Select Box with options 1-19
IO Class -> Select Box with options 1-3
IO Priority-> Select Box with options 1-7

1 means realtime and the higher the number the less important is the task.

Then this can be converted into custom commands depending on the user needs like:

nice -n{CPU PRIORITY} ionice -c{I/O CLASS} -n{I/O Priority} <backup task command>

For example one could set like this

nice -n19 ionice -c2 -n7 <backup task command>

Some useful functionalities of Backup in Web UI are not available in the XML API. Like configuring Password or Scheduled Backup. Those operations are at server level.

I think it would be useful to add the 4 following operations :

backup-manager / set-secure-backup-settings
backup-manager / get-secure-backup-settings

With attributes like :
- use-password-protection : boolean
- password : string

backup-manager / set-schedule-settings
backup-manager / get-schedule-settings

With attributes like :
- enable : boolean
- period : 86400 | 604800 |2592000
- hour : integer from 0 to 23
- minute : 0 | 15 | 30 |45
- use-incremental : boolean
- full-backup-period : 604800 | 2592000 | 31536000
- max-dump-files-unit : integer
- backup-content-mail : boolean
- backup-content-vhost : boolean
- repository : local | remote
- failure-notification : boolean
- failure-notification-email : string
- suspend : boolean

It can also be done by adding more attributes to existing operations.
For password, on xxx-remote-storage-settings.
For Scheduled Backup, on backup-server.