Akeeba Backup for Joomla!

Tuesday, 26 August 2025 15:59 CDT

UglyEoin

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 10MiB, please upload it on your server and post a link to it.

I don't want to take up my server space. I want to store things remotely.

I assume you create a local backup first and then fire it over to the remote.

I want a setting to remove that when uploaded successfully to the remote.

I have set the local quota to 1, but that seems to be the minimum. Over a lot of sites it takes up a lot of space, particularly for the larger sites.

Is there any chance you would consider making the limit 0 instead of 1?

Wednesday, 27 August 2025 01:02 CDT

nicholas

You are looking for the “Delete archive after processing” option under the Post-Processing Engine. The default for the past 15 years is Yes, i.e. the archive will be deleted upon successful upload.

The count quota will never be zero. It would allow someone to take a backup and have it automatically deleted after the backup is complete. This would apply on a local-only backup as well. And yes, we both know there are people out there who'd do exactly that.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 28 August 2025 08:12 CDT

UglyEoin

Interesting, then the JPAs on my site may be from unsuccessful backups, in which case... maybe we need a delete from unsuccessful backup or something?

Thursday, 28 August 2025 08:19 CDT

UglyEoin

Ok looks like that does actually remove the backup. So I'm not 100% sure why backups have been left on the server. I'll have to check my processes, maybe I've been creating local ones to migrate to dev and have not remembered to delete them.

Thursday, 28 August 2025 08:23 CDT

nicholas

Here's how I'd approach this.

First, check the log for the backup runs where the file remained. Look for "post-processing". If you see that the post-processing engine loaded is "none" it means that there was no backup archive uploading set up. Case closed in this case.

If you see a post-processing engine being loaded, you will then see in the log that Akeeba Backup tries to upload the archive. If there's a problem you'll see a warning and something along the lines that the upload was interrupted and will not be resumed. This means there was a problem preventing the archive upload. You can try to re-upload the backup archive using the upload button for this backup record in the rightmost column of the Manage Backups page.

It's also possible that the archive was uploaded, but your settings were telling Akeeba Backup to NOT remove it from local storage. This would also be logged.

If there are no log files, well, you can guess and speculate but we'll never really know.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 28 August 2025 11:47 CDT

UglyEoin

Thanks Nick, appreciate it.

I think I'll close this ticket for now and keep an eye on it, as it's probably a user error I imagine. The settings wouldn't have been changed from default so it won't be that.

Support