Multiple backup rules or more options
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.
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.
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.
Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.
Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:
#1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)
#2. Backup to different storages (like daily to FTP and monthly to Google Drive)
#3. Multiple Storages of the same type (like 2 different FTP servers)
ID in our Issue Tracker: PPM-1701
Maybe it comes with Plesk Smaragd :-D
Hope this will come soon. It‘s planned since 3 years? Why does it take so long? It‘s such an important thing to have…
For which century is this feature planned?
I would like to be able to pass the info to my descendants!
This topic is for feature suggestions not support. Try https://www.facebook.com/groups/plesk
Roma Sviridow commented
I had a failure in the backup, now I have to restore some of the data that was lost. What is the best way to do this? Can I use RAID Recovery https://www.diskinternals.com/raid-recovery/ or similar software?
K. Devlin commented
These tips were very useful to me, after I had to set up a backup, after a long time restoring files.
Oleg Burca commented
So annoying you have to build custom bicycles for so simple things!
Can you just add the possibility to have multiple backup schedules and some flexibility for retention policies?
Is it really so difficult?
Why is it taking that long.... we are all waiting for this...
Julia Lajos commented
jót joaron csk most
I am waiting too for this feature.
7 years waiting for this.
Francesco Zirconi commented
An more frequent backup option for database & mail should be nice.
Hi there. I hace also 4 vps with Plesk. And I have the package purchased to make backups. But still need to make backups to my Gdrive and to my local box here at the office (FTP Server). When will it be possible to make multiple backup rules for VPS or for each domain? So i can have one domain backed up in diferent locations
See that this is planned for quite some time now but still NO news. Hoping with the 2021 license increase price you can hire more manpower to make this happen.
Am I mistaken ? :-/
Please add this urgently, I have paid for scheduled cloud backup extension but cannot use it due to limitation of plesk backup schedule.
This is tagged as "PLANED" from 2014.... today is 2021, are you sure "planed" mean this?
Please add this options to Plesk! It's really important
Please add this options to Plesk.
Make per domain backups! No need to deal with a 300GB file if one client makes a mistake. But don't force me to activate the backups individually and configure individual backup space for each customer, how is that helping?
Luis Zubeldia commented
For our sanity, please enable the Plesk Migrator to also transfer the subscription Backup settings when migrated to a new server.
Since System-Dist-Upgrades are not advisable on production server, once in a while all customers/subscriptions etc. have to be migrated to a new node. But the backup settings are not transfered. Guess what, customers don't pay for you to add their backups settings back.
This shouldn't be to hard, since this is all in the database already.