Support

Akeeba Backup for Joomla!

#18691 Recovering automatic backup after joomla upgrade

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 morrispsych on Monday, 06 January 2014 09:12 CST

Monday, 06 January 2014 02:13 CST

morrispsych
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 2Mb, please upload it on your server and post a link to it.

Description of my issue: I cannot access the back end or front end of my site after attempting an upgrade from Joomla 2.5 to 3.2.1. The error message I am getting by setting max reporting through phpmyadmin is: Catchable fatal error: Argument 4 passed to JPluginHelper::importPlugin() must be an instance of JEventDispatcher, instance of KEventDispatcher given, called in /home/dpadalla/public_html/plugins/system/koowa/koowa.php on line 86 and defined in /home/dpadalla/public_html/libraries/cms/plugin/helper.php on line 148

While I know this problem is not caused by AkeebaBackup, I do need your help in finding out how to access the automatic site backup which Akeeba took prior to installing the Joomla upgrade which caused my site to be non-functional. If I can find a way to get the jpa file which I hope was created automatically, then I can use kickstart to get the site up and running again as it was prior to attempting the upgrade.

I am sorry that I cannot attach the Backup log file given that I cannot access the back end of the site.

Thanks for your help,

Michael

Monday, 06 January 2014 03:29 CST

nicholas
The backup archives are created in the configured backup output directory. If you've never defined something different, it's in administrator/components/com_akeeba/backup. If your default backup profile is set up to send the backup archives to an off-site storage (e.g. Dropbox, Amazon S3 etc) then this is where you should be looking for the files, not your server.

In any case keep copies of all backup archives. These files are your last chance to fix your site, if you lose them you're screwed. Being paranoid about them is a healthy thing: in cases like this I keep three copies, in different media (hard drive, NAS drive and a flash drive).

Then start by removing existing files and folders. If you skip that step you will be restoring Joomla! 2.5 on top of 3.2 which will result to a broken site. Finally just copy the .jpa file (and any other part files of the backup set, e.g. .j01, .j02 etc, if they are present) to the site root, upload Kickstart and start the restoration.

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!

Monday, 06 January 2014 09:12 CST

morrispsych
Nicholas,

Thank you so much for your help. The site is now restored, and I will take your advice on storing more than one backup in different locations.

Warm regards,

Michael

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!