Legacy backup retention doesn't work properly
Problem
I have found that when using the following settings in legacy backup:
Backup Interval: Weekly
Backup Retention: Weekly, Monthly
the backup runs weekly and monthly.
This means that you will not always have a "1 month ago" backup copy, because when the monthly backup runs, it overwrites the previous month's copy.
Why is this a problem?
I checked my backup copies, I only had July 5, 2015 for both weekly and monthly copies. If something went wrong with my sites today, I do not have a "1 month ago" backup copy to revert back to.
How it suppose to work
I believe since the setting says "Backup Retention" it should always have "1 month ago" backup copy.
-
Hello, When have you scheduled the weekly backup to run ? The retention keeps the backup of 1 months ago but it depends on which day you have set the backup to run. If you have setup wed, every month's first wed the monthly backup will get changed. Like in your case 5th July. 0 -
@24x7ss That is correct. But I am under the impression it will retain at least a "1 month ago" and also "1 week ago" copy at any given time since the setting says "retention". 0 -
Just following up on this. Is there a way to always have a "1 month ago" backup without using the new backup system? 0 -
Hello :) This issue is addressed with the new backup system. Could you elaborate on why you prefer to use the legacy backup system instead of the new backup system? Thank you. 0 -
Hello :) This issue is addressed with the new backup system. Could you elaborate on why you prefer to use the legacy backup system instead of the new backup system? Thank you.
The new backup system requires a large amount of free disk space for it work. So I, and presumably others who have limited disk space (specially SSD users) are still using legacy backup. Reference here:0 -
Note that we won't be making changes to the legacy backup system, so it's important to vote and add your feedback to the referenced feature request for the new backup system. Thank you. 0
Please sign in to leave a comment.
Comments
6 comments