Support

Akeeba Backup for Joomla!

#31824 Feature Request

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Friday, 01 November 2019 18:17 CDT

Brauneck
Hi Nicholas,

would it be possible to implement the display of the sum of memory consumption for the lokal (and perhaps also for the remote) jpa-Files in "Manage Backup"?

I think this feature would be very helpful for those who daily fight the battle against their disk quota ;)

It must be something like

SELECT SUM(total_size)/(1024*1024) AS MB FROM `#__ak_stats` WHERE filesexist = 1 , right?

Best regards,
Stefan

tampe125
Akeeba Staff
Hello,

we used to have it, but it's not accurate, since if you immediately upload the files, the size might be off.
Out of curiosity, why do you find yourself fighting with disk limits? Akeeba Backup has size quotas, you can tell him to start deleting old backups when their size is over a specific threshold.
Moreover, you can dodge disk limits by uploading the archives to a remote server and then delete the local archive.

Can you please tell me more about your use case?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Brauneck
Hi Davide,

first of all, the JPA-File are between ~ 500MB and 12 GB, depending on the frequency we backup (hourly to monthly), i.e. we are using serveral profiles (from "application core" DB tables to full installation). In case we have to restore a backup, we have to keep the downtime as short as possible. Therefore we keep the most recent backups on the local disk of the server since transfer rates to remote storages are not really fast. The next thing is, that the backup files of one profile may also vary a little bit dependend of the usage of the webpage.

Using the quota features of Akeeba Backup makes me feel to loose a little bit of control, because you never know, if a backup is still available locally.

It's be good to have the possibility to tag certain backups in a way that they are not deleted. In other words, it may not always be the case that the oldest backups are deleted.

Perhaps it's the best way for me, just doing a du -sh <outputdir> in a cronjob and let it email to me daily if the query above is not accurate enough.

(Just my thoughts)

Best regards,
Stefan

tampe125
Akeeba Staff
Yes, looking at your use case, I think that the easiest way for you is to run the cronjob and double check the size of all your backups.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!