I would like to have the ability to have say only my weekly or monthly backups be moved to the alternate location or perhaps just say every Sunday or another day of the week. IE instead of moving large backups over the wire on every backup, so send it offsite say once a week or monthly.
Seperate options to retain backups on different locations
Open Discussion
I like to have a possibility to keep only a few backups on the running server, but I need a bigger archive somewhere on a remote server. So if I set the local backup to retain 3 backups, the remote server doesn't keep any more backups either.
So I like to be able to set the option for how many backups I want to retain on the remote server, seperately from the local server.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Great idea.
Now, if I want have 1 weekly backup on local server and (for example) 6 weekly backups on remote server, the only option is activate the legacy backup for retain local backup and the new backup system for the remote backup without the option "Retain backups in the default backup directory.".
It would be very useful to use only the new backup system for this task, indicating for each backup (daily, weekly and monthly) the number of backups retained according to destination.
Great idea.
Now, if I want have 1 weekly backup on local server and (for example) 6 weekly backups on remote server, the only option is activate the legacy backup for retain local backup and the new backup system for the remote backup without the option "Retain backups in the default backup directory.".
It would be very useful to use only the new backup system for this task, indicating for each backup (daily, weekly and monthly) the number of backups retained according to destination.
I would like to both the schedule and retention policy setup moved to per-destination. I had a heavily modified cpbackup we used for years before the new backup system took hold. That system did a daily site rotation so we were sending off-site nightly but rotating which of multiple sites it went to. It was a bandwidth savings thing. Same was true of how it figured when and where to send monthly and weekly backups.
We use S3 now, but I wouldn't mind sending the monthly and weekly only to those other sites once again.
Defining the local retention policy separately from the remotes is important.
I would like to both the schedule and retention policy setup moved to per-destination. I had a heavily modified cpbackup we used for years before the new backup system took hold. That system did a daily site rotation so we were sending off-site nightly but rotating which of multiple sites it went to. It was a bandwidth savings thing. Same was true of how it figured when and where to send monthly and weekly backups.
We use S3 now, but I wouldn't mind sending the monthly and weekly only to those other sites once again.
Defining the local retention policy separately from the remotes is important.
I would love this solution a.s.a.p and have an additional suggest too.
I want to save more backups on external box, but only be able to
save same amount of backups as setup on on local server. As well the backups should be able to delete the older once on external box too according tot the retain setup done.
I would love this solution a.s.a.p and have an additional suggest too.
I want to save more backups on external box, but only be able to
save same amount of backups as setup on on local server. As well the backups should be able to delete the older once on external box too according tot the retain setup done.
It makes no sense that this functions as such. The whole point of remote backups is to remove them from your server. Why wold you have the same quotas for local and remote?
It makes no sense that this functions as such. The whole point of remote backups is to remove them from your server. Why wold you have the same quotas for local and remote?
I stated some of this previously, but I've also commented on other backup threads. My dream is to be able to set separate retention policies for each remote site as well as the local retention. We build our servers with a secondary backup drive that's double the size of the /home drive. We do keep the backups local and want to retain that. a) It provides additional redundancy in the event of a catastrophic failure at a remote site. b) A restore of an individual account can be handled quickly while still having full DR capability off-site.
I stated some of this previously, but I've also commented on other backup threads. My dream is to be able to set separate retention policies for each remote site as well as the local retention. We build our servers with a secondary backup drive that's double the size of the /home drive. We do keep the backups local and want to retain that. a) It provides additional redundancy in the event of a catastrophic failure at a remote site. b) A restore of an individual account can be handled quickly while still having full DR capability off-site.
It would never have occurred to me that that the retention quota would impact remote ones. This really needs to change.
It would never have occurred to me that that the retention quota would impact remote ones. This really needs to change.
While it would be great if cPanel did splut this up, or allowed us to create "backup jobs" like other systems use that would let us create a "local" backup job and a "remote" backup job. this would allow us to have much greater control over things and for example let us choose to keep 7 local backups but store 30 remote backups etc.
Not sure If I am allowed to post this (so please dont ban me if I'm not!) but we have just started using Jet Backup as it provides this functionality amongst other things
If cPanel could improve the backup system to provide these kind of extensive options and functionality it would be great.
While it would be great if cPanel did splut this up, or allowed us to create "backup jobs" like other systems use that would let us create a "local" backup job and a "remote" backup job. this would allow us to have much greater control over things and for example let us choose to keep 7 local backups but store 30 remote backups etc.
Not sure If I am allowed to post this (so please dont ban me if I'm not!) but we have just started using Jet Backup as it provides this functionality amongst other things
If cPanel could improve the backup system to provide these kind of extensive options and functionality it would be great.
Yes, we need two remote profiles (or more) e.g. weekly backup to S3 and daily backup to another (e.g. Google Drive or Dropbox).
Thanks
Yes, we need two remote profiles (or more) e.g. weekly backup to S3 and daily backup to another (e.g. Google Drive or Dropbox).
Thanks
It would be nice if we could retain only the last backup on the local server but configure a different retention policy for other destinations. This would greatly improve the speed to recover the last backup.
It would be nice if we could retain only the last backup on the local server but configure a different retention policy for other destinations. This would greatly improve the speed to recover the last backup.
Is there any update on this?
Is there any update on this?
Yeah ... I'll update my previous comment. We've moved to VPS's where we no longer maintain a secondary 2x drive for local backup retention. We're all remote now.
I see I've finally found my original comments on this destination retention topic (I knew I dropped them somewhere). There's a couple related topics I've dropped this as well. To quote one of my earlier posts: "Defining the local retention policy separately from the remotes is important."
Yeah ... I'll update my previous comment. We've moved to VPS's where we no longer maintain a secondary 2x drive for local backup retention. We're all remote now.
I see I've finally found my original comments on this destination retention topic (I knew I dropped them somewhere). There's a couple related topics I've dropped this as well. To quote one of my earlier posts: "Defining the local retention policy separately from the remotes is important."
Definitely would be a handy feature to have! We're stuck with no local backup to keep our remotes set to a really high retention with unlimited storage on Google Drive. The big reason for us that this feature would be killer is having 1-2 locals backups would immensely speed up recovery for larger accounts.
Definitely would be a handy feature to have! We're stuck with no local backup to keep our remotes set to a really high retention with unlimited storage on Google Drive. The big reason for us that this feature would be killer is having 1-2 locals backups would immensely speed up recovery for larger accounts.
📜 Once upon a time, cPanel had only local backup and the Wizards rejoiced for they knew the importance of enchanting data into a Backup.
Then, Cloud Computing was invented and Amazon brought cheap-ass storage to the masses. The Wizards rejoiced but then had to petition cPanel to add a charm to the Backup Configuration so that Backups could take a magical journey to Amazon for sanctuary. The Council of cPanel granted the plea and all were contented.
Then the virtual kingdoms were invaded by brutes who cast malicious spells on the data, holding it hostage for ransom. The Wizards increased the retention of their backups in order to fortify their sanctuary, but quickly realized that they did not have enough room in the kingdom to maintain the growing tome of sanctuary.
Once again, the Wizards came before cPanel to petition the creation of another charm, one that allows the Wizards to control the size of their sanctuary both at home and separately at their haven far, far away.
And now the Wizards await the consensus from the Council of cPanel so that this spell will emerge from the backlog, allowing the Wizards to achieve a deep slumber between the raids of the brutes who bring evermore powerful weaponry.
To be continued ... ?
📜 Once upon a time, cPanel had only local backup and the Wizards rejoiced for they knew the importance of enchanting data into a Backup.
Then, Cloud Computing was invented and Amazon brought cheap-ass storage to the masses. The Wizards rejoiced but then had to petition cPanel to add a charm to the Backup Configuration so that Backups could take a magical journey to Amazon for sanctuary. The Council of cPanel granted the plea and all were contented.
Then the virtual kingdoms were invaded by brutes who cast malicious spells on the data, holding it hostage for ransom. The Wizards increased the retention of their backups in order to fortify their sanctuary, but quickly realized that they did not have enough room in the kingdom to maintain the growing tome of sanctuary.
Once again, the Wizards came before cPanel to petition the creation of another charm, one that allows the Wizards to control the size of their sanctuary both at home and separately at their haven far, far away.
And now the Wizards await the consensus from the Council of cPanel so that this spell will emerge from the backlog, allowing the Wizards to achieve a deep slumber between the raids of the brutes who bring evermore powerful weaponry.
To be continued ... ?
Replies have been locked on this page!