Support

Akeeba Backup for WordPress

#34390 – Quota Management / Expired Backups are not deleted

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Wednesday, 20 January 2021 09:57 CST
itsonlycomputers

I have a number of sites where the Quota management is not working and backups are not being deleted. Sites are hosted on different hosting providers (Ionos, Siteground, Godaddy).

I am attaching my configuration for your review.   I do have a firewall installed (All In One WP Security), not sure if there is a conflict with a script or what.

Any ideas on what to check?  Happy to provide access if required.

Thanks

 

 

Custom Fields

WordPress version (in x.y.z format) 5.6
PHP version (in x.y.z format) 7.4.14
Akeeba Backup version (x.y.z format) 7.5.1
 
Wednesday, 20 January 2021 10:08 CST
nicholas

We are using quotas on all of our sites (production, test and development) without having observed any such behaviour. I am mostly inclined to believe that there is a misunderstanding about how the quota feature works and what it does. In fact this is what the vast majority of similar ticket is. Moreover, I see at least two problems in your setup.

First of all, quotas are applied against backup records, not backup archive files. If it's not listed in Manage Backups page it does not participate in quota management.

You have selected to keep 1 obsolete record. "Obsolete" means that the backup archive is not present on your server. Since remote backup records are obsolete by definition you are only keeping the latest backup record. Therefore the quotas are applied only on the latest backup record. This means that they will never be satisfied and nothing will be deleted.

Quotas are only applied to backup records taken with the same backup profile. You cannot apply quotas across different backup profiles.

Whether remote quotas can be applied depends on which Post-processing engine you are using and in many cases the permissions you give to the user which you connect to Akeeba Backup. For example, if you use FTP or SFTP but your user does not have delete privileges (e.g. the folder has the sticky bit set) you won't be able to delete remotely stored files. Amazon S3 allows you to create write-only users therefore the quotas cannot be applied because Akeeba Backup does not have delete privileges.

You have also set both maximum age and count quotas. This is a bad idea. Count quotas would delete backups which are spared by the maximum age quotas.



Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Wednesday, 20 January 2021 12:03 CST
itsonlycomputers

Thank you for this excellent explanation!

 

 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!