Support

If you are receiving a blank page after installing an alpha release of Akeeba Backup, you have a partial installation. We will have to log you back into your site and have you either reinstall the same version of Akeeba Backup (fixing the partial installation) or downgrading to the previous stable release.

1. Logging back into your site:
Please start by removing the administrator/modules/mod_akadmin directory first and retry logging back into your site. If that doesn't work, remove the following folders:
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction
By doing that you have uninstalled all Akeeba Backup code. If the problem persists, your inability to login is unrelated to Akeeba Backup.

2.A. Reinstalling Akeeba Backup:
If you are logged in, please try disabling the "System - System Restore Points" plugin (if it's installed and enabled), then try downloading and installing the same version of Akeeba Backup as the one you already have. Now your component will work

2.B. Downgrading Akeeba Backup:
You MUST NOT try to install an older version of Akeeba Backup on top of a new one. It will cause backup errors or other problems with your site. Instead, start by removing the following directories:
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction
Only now should you attempt to install an older version of Akeeba Backup.

Hi Ken,

This usually happens when your account goes over quota. I had to ask the owner of the hosting company I'm using about this issue (which had actually happened to another user, not me) a few months ago. He told me that when an account hits its quota limit, any attempt to write to files may result in 0-byte files. Another way I've managed to cause this problem on a test server was when its filesystem got corrupt after a series of hard resets. The only way to fix that is restoring a backup. If you don't have a recent backup, you'll have to rely to your host's backups.

You might be able to do a partial restoration and a subsequent upgrade. It would go like this:
- First take a backup of your database tables using phpMyAdmin, just in case something happens
- Remove Joomla!'s directories and files from the site
- Extract the backup but do not proceed with the actual restoration (do not overwrite your database)
- Remove the installation directory
- Log in to your site's back-end
- Install Admin Tools 2.2.a3
- Upgrade the site to Joomla! 2.5.4
- Install Akeeba Backup 3.4.3 if not already installed
- Take a backup of the site and keep it somewhere safe
- Wait for me to release the stable release 3.5.0 of Akeeba Backup before updating your copy of Akeeba Backup

Yes, my way will mean that 1.7 will run with the db of 2.5. I don't any reason for that to fail, as 2.5 merely added a few more tables, it didn't change the database schema.

Stop the restoration right before clicking on the "Run the installer" button.

Is it safer to do the restore, and then upgrade, and then just tell joomla to switch databasesin Global Configuration?

You can also do that, of course. Maybe it's safer.

The partial restore will restore all backed up files, including all of the images contained in the backup.

You have to use Admin Tools 2.2.a3. Later versions (including the current version 2.2.5) do not support Joomla! 1.7 and will not detect the updates at all. Uninstall your copy of Admin Tools and install Admin Tools 2.2.a3.