cPanel & WHM Version 92 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Limit backup time interval

David Heremans shared this idea 6 years ago
Open Discussion

Hi,


At this time, we can only set up the cron start time for a new backup process.

However, on a relatively large server when there is lots of data that requires backing up, it can mean that it's still running in the morning at peak hours.


To prevent this, I'd like to see the possibility to set up a time interval in which backups can be run (preferably configurable per day, because on sunday we may decide to keep it running longer than on weekdays...)


Since that would mean that not all backups may be completed by the time the time interval is nearing its end, I believe it's much needed that you keep additional metadata on the backups (at least the "latestbackuptimestamp" for each account) Whenever a new backup process is started, it should iterate over all accounts, but sorted by "latestbackuptimestamp" (and putting them with NO timestamp first!) This would ensure that accounts that - for whatever reason - did not have their backup correctly taken yesterday, would sure be backed up today.

Comments (3)

photo
1

We'd like to hear some additional feedback on this request. A concern to consider with this feature is that a server could perpetually be behind on backups if the backup isn't completed in the designated timeframe.

photo
1

cPScottT wrote:

We'd like to hear some additional feedback on this request. A concern to consider with this feature is that a server could perpetually be behind on backups if the backup isn't completed in the designated timeframe.
That's true, and that is why I added the information on additional metadata, and the request to start backing up the accounts that we have the least recent backups of when we start a new backup run.


If would be added like this, combined with my additional reporting on backup requests, we could easily see how much behind we are... and if a hoster wants the absolute certainty that backups are ALL done; he would imply be putting 00:00 -> 23:59 :-)


I don't think that concern should be a reason not to implement such a feature. They key concern of this feature request in my opinion is that servers are unworkable if backups are still running at peak times, and that results in almost instant complaints from customers :-)

photo
1

David Heremans wrote:

That's true, and that is why I added the information on additional metadata, and the request to start backing up the accounts that we have the least recent backups of when we start a new backup run.


If would be added like this, combined with my additional reporting on backup requests, we could easily see how much behind we are... and if a hoster wants the absolute certainty that backups are ALL done; he would imply be putting 00:00 -> 23:59 :-)


I don't think that concern should be a reason not to implement such a feature. They key concern of this feature request in my opinion is that servers are unworkable if backups are still running at peak times, and that results in almost instant complaints from customers :-)

Also, considering that it should be able to backup at least half of the accounts within the specified time interval, the backups would be behind 2 days MAX for one particular account. We, for instance, do take backups, and they are much needed, but it needs to remain workable as well. I have a server that has 400 accounts, around 90 GB of data. This server has no issues at all to process 6TB of data traffic a month, with some wordpress installations, and magento installations on there. It has 32GB of RAM and enough processing power. Yet the backup takes 12+ hours to complete. I can not go to my customers and say that the server is not responding due to backups running :-)