Support

Akeeba Backup for Joomla!

#43038 It's not your fault I'm an idiot but we could still protect the idiots

Posted in ‘Akeeba Backup for Joomla!’
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
6.1.0
PHP version
8.3
Akeeba Backup version
10.3.3

Latest post by nicholas on Wednesday, 17 June 2026 06:34 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.

Hands up, I'm an idiot. I fixed all my client sites with the JCE issue except my own. Face palm. I then dutifully went to Amazon S3, only to find no backups were there. Yay. Upon logging in I saw my S3 profile was set to no post processing. For the last few years. I have no idea how. The good news is, my daily CRON has been running, and I did indeed have all the backups. The bad news is I had nuked my site files and folders because I wanted a fresh install not an install over the top. Fortunately there were all in my cPanel's .trash folder. Yay. I'm saved. I copied them all to my root so I could start working out which one was far enough back not to be hacked. I restored a backup using kickstart, clicked "clean up files" and it wiped all the old backups. But the restoration was still a hacked website. DOH. I needed to go back further. And now the backups are not in trash. So I guess my point is, often for a hacked website we often don't know which version to restore, it's a bit of trial and error. Is there a way to clean up all files except backups? That would be useful in times like this. I know my ADHD ass clicks too fast and this is totally my fault, but I think this might be a use case for this feature.

nicholas
Akeeba Staff
Manager

In an ideal world: You have a disaster recovery plan you have written down in advance, and which you have tested thoroughly on both staging and live infrastructure. When you get hacked you don't panic. You go to your site's backend and check which backups are taken before doing anything else. You make sure all these backups are downloaded and copied to a flash drive. Then you start acting.

In the real world: Poop hits the fan, making everyone and everything look like a rather fecal interpretation of a Jackson Pollock painting. Still, you need to make sure you have a copy of your backups. No backups = bad times. This is the one bit I can't help with.

Now, restoring a site does NOT delete backup archive files by default. You'd have to explicitly select the option to delete files on the server for that to happen – which is strategically placed as far away from the green start button as possible, giving you more than an ohnosecond to realize what you're doing, stop, and finally download those blasted backups before continuing. I don't suppose you are stupid. I suppose we all are stupid under stress. It's not the same.

What will get overwritten, of course, is the contents of the #__akeebabackup_backups table during restoration. However, I do give you the option to tell the Akeeba Backup Restoration Script which tables to restore in the database restoration page (right hand side). By extension, you can select all tables except for the #__akeebabackup_backups table.

Further to that, remember how I told you that you should download those backup archives? If you have the backup archives locally, you can extract them. Either use a local web server to run Kickstart, or run it through the command line. You can now inspect the contents of each extracted backup archive. Once you find the clean backup, copy it to a new flash drive, put it in an envelope, seal it, and put it in your drawer. Delete all files on your site, upload the clean backup and Kickstart, do the restoration. Oh, oops, you messed that up, eh? It happens. No problem. Delete all files from the site, retrieve the sealed envelope from your desk muttering to your yourself about bleeping [unprintable] muppet, get the flash drive, upload the correct backup this time, do the restoration. Sounds about right? :)

And for the bewildered people reading this public ticket and wondering why I have it out for Eoin. Chill out, I know Eoin. We have the same deviant sense of humour. The core of the instructions holds true. The humourous parts are just a bit of fun to lighten the mood.

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!

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!