This object is in archive!
purging of incremental backup
Needs Review
Please implement automatic purging of increment backups as a feature. Thx
- [cPanel tickets ID# 5271915] Re: Clean Up Incremental Backup Directory
- From: Zachary Karr <tickets@cpanel.net>
- To: me
- Hello,
- Due to the way the incremental backups currently function, any file in the cpbackup-exclude.conf file will be skipped in the backups. This means it will not check if there is a newer version of the file in the backups or not.
- Based on my testing the older, pre-exclude, file will still remain in the backups. In order to "clean up" the incremental directory the files would need to manually be removed.
- --Sincerely,
- Zachary Karr
- Technical Analyst I
- cPanel Inc.
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.
This is not a feature that will be considered for inclusion into the product. For historical reference, this has been previously discussed internally via Case 49946. The result of which was the decision that this is intentional and by design, that we want any files that were (but no longer are due to the 'exclude') managed by cPanel backups to be manually removed by the server administrator.
Essentially, this simply requires the one additional step of removing the data you want to exclude from the backups at the same time you add them to the exclude file. The reasoning behind this stems from cPanel & WHM wanting to err on the side of keeping data versus potentially deleting desired data from customer boxes.
This is not a feature that will be considered for inclusion into the product. For historical reference, this has been previously discussed internally via Case 49946. The result of which was the decision that this is intentional and by design, that we want any files that were (but no longer are due to the 'exclude') managed by cPanel backups to be manually removed by the server administrator.
Essentially, this simply requires the one additional step of removing the data you want to exclude from the backups at the same time you add them to the exclude file. The reasoning behind this stems from cPanel & WHM wanting to err on the side of keeping data versus potentially deleting desired data from customer boxes.
This is not a feature that will be considered for inclusion into the product. For historical reference, this has been previously discussed internally via Case 49946. The result of which was the decision that this is intentional and by design, that we want any files that were (but no longer are due to the 'exclude') managed by cPanel backups to be manually removed by the server administrator.
Essentially, this simply requires the one additional step of removing the data you want to exclude from the backups at the same time you add them to the exclude file. The reasoning behind this stems from cPanel & WHM wanting to err on the side of keeping data versus potentially deleting desired data from customer boxes.
This is not a feature that will be considered for inclusion into the product. For historical reference, this has been previously discussed internally via Case 49946. The result of which was the decision that this is intentional and by design, that we want any files that were (but no longer are due to the 'exclude') managed by cPanel backups to be manually removed by the server administrator.
Essentially, this simply requires the one additional step of removing the data you want to exclude from the backups at the same time you add them to the exclude file. The reasoning behind this stems from cPanel & WHM wanting to err on the side of keeping data versus potentially deleting desired data from customer boxes.
Replies have been locked on this page!