Forgot your username?             Forgot your password?

Want more?

Our Core versions are provided free of charge, but they only scratch the surface of what's possible. Subscribe today to get access to the exclusive features and enhanced support of our Professional releases!

Subscribe Already a subscriber? Log in.

Akeeba Backup for Joomla!

Here you will find the downloads to Akeeba Backup for Joomla!, our award-winning full site backup and transfer component for Joomla!. Both the Core (free) and Professional (paid) editions can be found in here.

Download and install translation files from our translations page

Stable 4.2.4

Maturity:
Stable
Released on:
Monday, 22 June 2015 19:00
Viewed:
21450 times

This is a bugfix and features release of Akeeba Backup, solving some issues regarding restoration of sites on different MySQL versions and an issue affecting uploads to Dropbox on PHP 5.5 and 5.6.

Alternatives to obsolete features removed in 4.2.0

Since Akeeba Backup 4.2.0 the features deprecated since 4.0.0 have been removed. Below you can find alternatives if you miss the functionality and need an equivalent solution.

Post-setup page. All messages are now handled through Joomla!'s Post-Installation Messages component. This change first appeared in Akeeba Backup 4.0 when installed on Joomla! 3.2 and later. Now this is now the only way to review the post-installation messages.

Site Transfer Wizard. The wizard didn't make site transfers possible, it only helped you set up the backup profile. You can still use the DirectFTP and DirectSFTP archiver engine to the same effect – after all, that's the only thing the wizard did for you, enable these archiver engines. However we recommend using regular JPA or ZIP backup archives with the Upload to FTP and Upload to SFTP post-processing engines along with the Upload Kickstart option. This new method is much more stable and far less likely to fail midway through the site transfer.

System Restore Point and Extension Filters. These two features were removed for the same reason: since Joomla! 1.6 it is no longer feasible to backup and restore, or even exclude, a single extension of your site. Joomla!'s ACL system means that everything in it (articles, categories, extensions and even third party items) are linked together through the #__assets table. On top of that, the Tags and Content Versioning features added in Joomla! 3.1 and 3.2 respectively made everything also depend on the UCM set of tables. Due to the way these tables are constructed it's impossible to make a complete backup of an extension's state without also backing up the entire system states. This makes the System Restore Points either incomplete backups (they were, indeed) or would make their restoration potentially kill your site (we didn't go that way for obvious reasons). Furthermore, removing a single extension would either leave behind orphan records or create holes in the tables, both options leading to database inconsistencies which could make your site fail to work correctly. For these reasons we removed both features and have to note that no, they DID NOT work properly in Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3 and 3.4; no, they cannot be fixed (what do you think we were trying to do the last four years?); and no, they are not coming back exactly because they DO NOT work and CAN NOT be made to work. There is no alternative. We recommend simply taking full backups of your site before any major change such as upgrading to a new major version of an extension.

Lite Mode. This feature was developed back when featurephones with limited web browsers were the norm. In the eight years which have elapsed since that time smartphones with full featured browsers became the norm, Joomla! became responsive and other mobile devices with full features web browsers (tablets, netbooks / mini-laptops such as the 2015 MacBook, two-in-ones such as Microsoft Surface Pro etc) have emerged. For this reason the easiest, most stable and outright convenient way to back up your site while on the move is logging in to the backend of your Joomla! 3 site from your mobile device and use Akeeba Backup normally. Our interface is responsive and touch-optimised since mid-2012!

Joomla! 3.3/3.4 only

Only Joomla! 3.3 and 3.4 (and 3.5 which is planned for release in a couple of months) is supported by this version. We strongly recommend using the latest Joomla! At the time of this writing it is 3.4.1. Using older versions is NOT recommended for security reasons.

PHP 5.3.4 or later 5.x version is required

This version requires PHP 5.3.4 or later (e.g. 5.3.29 which is twenty five versions newer than PHP 5.3.4), 5.4, 5.5 or 5.6. Please note that PHP 5.3 is obsolete since August 2014 and we're going to stop supporting it without warning in future versions of our software. We'd like to remind you that Joomla! 3.x does not currently support PHP 7. Since our software runs inside Joomla! by definition our software doesn't currently run on PHP 7 either.

Note: there is no such thing as PHP 6. PHP versions jumped from 5.6 to 7.0. Why? Well, it's a long story. TL;DR: It doesn't have to make sense, just accept it.

Changelog

Bug fixes

  • [HIGH] Restoring on MySQL would be impossible unless you used the MySQL PDO driver
  • [LOW] Desktop notifications for backup resume showed "%d" instead of the time to wait before resume
  • [LOW] Push notifications should not be enabled by default
  • [MEDIUM] Dropbox integration would not work under many PHP 5.5 and 5.6 servers due to a PHP issue. Workaround applied.

New features

  • Support utf8mb4 in CRON jobs

Miscellaneous changes

  • ANGIE: Improve memory efficiency of the database engine
  • Switching the default log level to All Information and Debug

Take me to the downloads for this version

Stable 4.2.3

Maturity:
Stable
Released on:
Wednesday, 10 June 2015 06:47
Viewed:
10300 times

This is a bugfix and maintenance release, addressing known issues and introducing minor improvements.

Release highlights

Joomla! 3.3 and 3.4 only. We discontinued Joomla! 2.5 support in January 2015 as previously announced.

Desktop notifications: You will receive notifications on your desktop when the backup starts, issues a warning / error or finishes successfully. Please note that this feature requires a compatible browser. At the time of this writing Chrome, Firefox and Safari support desktop notifications.

UTF8MB4 (UTF-8 multibyte) support in restoration scripts: Supports databases able to display quad byte UTF-8 characters such as Emoji and the less common Traditional Chinese glyphs.

Bug fixes: There is a really important one affecting your ability to restore a backup if your old database password contains double quotes. Some minor issues and enhancements regarding remote storage services are also included.

Alternatives to obsolete features removed in 4.2.0

Since Akeeba Backup 4.2.0 the features deprecated since 4.0.0 have been removed. Below you can find alternatives if you miss the functionality and need an equivalent solution.

Post-setup page. All messages are now handled through Joomla!'s Post-Installation Messages component. This change first appeared in Akeeba Backup 4.0 when installed on Joomla! 3.2 and later. Now this is now the only way to review the post-installation messages.

Site Transfer Wizard. The wizard didn't make site transfers possible, it only helped you set up the backup profile. You can still use the DirectFTP and DirectSFTP archiver engine to the same effect – after all, that's the only thing the wizard did for you, enable these archiver engines. However we recommend using regular JPA or ZIP backup archives with the Upload to FTP and Upload to SFTP post-processing engines along with the Upload Kickstart option. This new method is much more stable and far less likely to fail midway through the site transfer.

System Restore Point and Extension Filters. These two features were removed for the same reason: since Joomla! 1.6 it is no longer feasible to backup and restore, or even exclude, a single extension of your site. Joomla!'s ACL system means that everything in it (articles, categories, extensions and even third party items) are linked together through the #__assets table. On top of that, the Tags and Content Versioning features added in Joomla! 3.1 and 3.2 respectively made everything also depend on the UCM set of tables. Due to the way these tables are constructed it's impossible to make a complete backup of an extension's state without also backing up the entire system states. This makes the System Restore Points either incomplete backups (they were, indeed) or would make their restoration potentially kill your site (we didn't go that way for obvious reasons). Furthermore, removing a single extension would either leave behind orphan records or create holes in the tables, both options leading to database inconsistencies which could make your site fail to work correctly. For these reasons we removed both features and have to note that no, they DID NOT work properly in Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3 and 3.4; no, they cannot be fixed (what do you think we were trying to do the last four years?); and no, they are not coming back exactly because they DO NOT work and CAN NOT be made to work. There is no alternative. We recommend simply taking full backups of your site before any major change such as upgrading to a new major version of an extension.

Lite Mode. This feature was developed back when featurephones with limited web browsers were the norm. In the eight years which have elapsed since that time smartphones with full featured browsers became the norm, Joomla! became responsive and other mobile devices with full features web browsers (tablets, netbooks / mini-laptops such as the 2015 MacBook, two-in-ones such as Microsoft Surface Pro etc) have emerged. For this reason the easiest, most stable and outright convenient way to back up your site while on the move is logging in to the backend of your Joomla! 3 site from your mobile device and use Akeeba Backup normally. Our interface is responsive and touch-optimised since mid-2012!

Changelog

Critical bugs and important changes

  • Packaging error leading to immediate backup failure

Take me to the downloads for this version

Stable 4.1.2

Maturity:
Stable
Released on:
Monday, 02 February 2015 18:00
Viewed:
63224 times

The most major issue fixed affect sites hosted on really bad hosts which block the innocent parse_ini_file() PHP function when they really meant to block the ini_set() function which can have security implications on very badly configured servers. In other words if you didn't see most interface icons with Akeeba Backup 4.1.0/4.1.1 you are hosted on a really bad host who has no idea about PHP security. In this case we strongly recommend you to immediately move your site to a decent host, for security reasons.

Additionally we fixed some issues affecting the restoration and a high priority issue which would result in the partial inclusion of the restoration script (with a warning), making it impossible to perform a proper restoration.

Finally, we'd like to remind you that this is the last version of Akeeba Backup with Joomla! 2.5 support. Future versions will only support the latest Joomla! 3 release.

Bugfix release

This is a bugfix release of Akeeba Backup. The most major issue fixed affect sites hosted on really bad hosts which block the innocent parse_ini_file() PHP function when they really meant to block the ini_set() function which can have security implications on very badly configured servers. In other words if you didn't see most interface icons with Akeeba Backup 4.1.0/4.1.1 you are hosted on a really bad host who has no idea about PHP security. In this case we strongly recommend you to immediately move your site to a decent host, for security reasons.

Additionally we fixed some issues affecting the restoration and a high priority issue which would result in the partial inclusion of the restoration script (with a warning), making it impossible to perform a proper restoration.

Changelog

Bug fixes

  • [HIGH] ANGIE (restoration): Some bad hosts disable the innocent parse_ini_file PHP function resulting in translation and functional issues during the restoration
  • [HIGH] Missing interface options on bad hosts which disable the innocent parse_ini_file PHP function
  • [LOW] ANGIE for Wordpress: fixed changing Admin access details while restoring
  • [LOW] Configuration Wizard: detected minimum execution time was ignored; default value of 2 seconds always applied
  • [LOW] On some hosts you wouldn't get the correct installer included in the backup
  • [MEDIUM] ANGIE for Wordpress: Site url was not replaced when moving to a different server

New features

  • ANGIE for Wordpress: Db collation set to "utf8_general_ci" by default
  • Added "Apply to all" button in Files and Directories Exclusion page

Take me to the downloads for this version

Stable 4.0.5

Maturity:
Stable
Released on:
Tuesday, 30 September 2014 15:14
Viewed:
66342 times

This is a regular maintenance release of Akeeba Backup.

Release highlights for this version

Fixed issues with backups on Windows hosts using PHP 5.3. There is a bug on PHP 5.3 on Windows regarding the handling of open files which would cause an error regarding renaming the last part to .JPA when using a non-zero Part Size for Split Archives on a Windows host running PHP 5.3. This version of Akeeba Backup works around the PHP bug. To the best of our knowledge PHP 5.4, 5.5 and 5.6 on Windows, as well as all versions of PHP on Linux and Mac OS X are not affected by this bug.

Important note about RackSpace CloudFiles

Throughout September 2014 and at least until the time of this writing (September 13th, 2014) RackSpace is experiencing severe issues with their API stability. Even though all information you have entered in our software is correct you may get authentication, timeout or upload errors. This is not a bug in our software and we have no control over it. This is an issue with RackSpace and affects all software trying to connect to CloudFiles (e.g. CyberDuck). Moreover, the issues seem to be of an intermittent nature, both regarding time and region. Please do not file support requests and bug reports concerning CloudFiles. We will ignore them until we have determined that CloudFiles works consistently for at least 48 hours straight.

Release highlights for version family 4.0

Resumable backups. If a back-end backup halts with an AJAX error, Akeeba Backup will try resuming it. This allows the backup to complete when it halted due to a temporary network or server issue.

One log per backup attempt. On popular request, a different log file will be created for each backup attempt. This allows you to examine the impact of your configuration changes between backup attempts.

Simultaneous backups. You can now execute several backups at the same time using the front-end, remote JSON API and CLI methods. You are still only able to execute one back-end backup at a time for reasons that have to do with the Joomla! session management and the way browsers work.

Client-side minimum execution time delay. You can now have your browser enforce the minimum execution time preference. This reduces the processor load on the web server, allowing you to take more reliable backups on restrictive shared hosts.

Improved AJAX URL randomisation. The randomisation part of the AJAX action URL has been improved to avoid issues with the security rules of certain hosts. Essentially we will be avoiding cases similar to what happened with GoDaddy in June 2014.

Massive performance boost on large tables. You will observe a massive performance boost when backing up tables larger than a few thousand rows. This might shave up to 85% of the backup time of sites with huge database tables.

Work-arounds for several issues with third party code. We have devised and implemented workarounds for badly written third party code affecting Javascript execution on the page, as well as the badly written error pages of some hosts which contain page-modifying Javascript. Moreover we have worked around the majority of extremely zealous password managers which will auto-fill an irrelevant password into the ANGIE password and/or JPS password fields in the Configuration page without asking you, without letting you know, despite us using the standard autocomplete="off" attribute to let the browser know that it should never auto-fill that field. Our solution is to make the page slower to load and include a lot of delayed Javascript to reset the fields after the browser auto-fills them.

Support for the new MySQL (PDO) driver in Joomla! 3.4. That's right, we support Joomla! 3.4 before it's even released! Akeeba Backup 4.0.0 is designed to support the new MySQL PDO database driver which will be included in the upcoming Joomla! 3.4.0, due for release towards the end of September 2014.

Less hassle. Remember the Post-installation Configuration page you had to go through after each and every installation or update of Akeeba Backup? If you have Joomla! 3.2.0 or later (including 3.3.x and 3.4.x) you will no longer have to put up with it. We are now using the Post-installation Messages component included with Joomla! to display and manage the post-intallation / post-upgrade messages of our component.

Help us get more insight. Our software includes code to anonymously report your PHP, MySQL, Joomla! and Akeeba Backup version. This information cannot be linked to a particular site or person. It will help us get a glimpse at which versions are in use in real world servers, in what relative percentage, and let us to better plan our deprecation strategy. If you don't wish to take part to this anonymous data collection you can opt out from the component's Options page at any time.

PHP 5.3, 5.4, 5.5 or 5.6 is required

This version requires PHP 5.3, 5.4, 5.5 or 5.6. The rationale behind this is explained in our statement of mid-February 2013. It won't install on hosts running PHP 5.2 or earlier. PHP 5.3.4 or later is required, due to show-stopper bugs in earlier versions of PHP 5.3. Important note on reading PHP versions: PHP 5.3.20 is newer than 5.3.10 which is newer than 5.3.4. Moreover, PHP 5.4.0 is newer than PHP 5.3.4.

Due to the necessary Joomla! API changes found only in Joomla! 2.5.6 or later, this version will not install on Joomla! 2.5.5 or earlier versions. In any case, if your server doesn't meet the minimum requirements it will tell you exactly why it cannot be installed (minimum PHP or Joomla! version not satisfied).

Joomla! 2.5, 3.2, 3.3, 3.4 are supported

This version of our software can be installed on Joomla! 2.5.6 or any later 2.5.x release, as well as any 3.2.x, 3.3.x or 3.4.x release. It is not compatible with Joomla! 3.0 or 3.1. These versions of Joomla! are old and vulnerable. If you are using them please upgrade to the latest Joomla! 3 release available from Joomla.org.

Changelog

Bug fixes

  • [HIGH] The integrated restoration is broken after the last security update

Take me to the downloads for this version

Stable 3.2.10

Maturity:
Stable
Released on:
Monday, 29 September 2014 19:00
Viewed:
18760 times

This is a security release addressing a high impact, but very unlikely, security issue with the Professional version's integrated restoration feature. All Professional users are advised to upgrade. For more information please consult our news article.

Please note that this old release of Akeeba Backup is end of life and no longer supported. This security fix is provided as a courtesy and does not imply that we will provide any kind of support for it.

Please consult our news article.

Additional note: this version also allows the software to run on servers using MySQL 5.6 or later.

Take me to the downloads for this version

Stable 3.4.6

Maturity:
Stable
Released on:
Monday, 29 September 2014 19:00
Viewed:
26149 times

This is a security release addressing a high impact, but very unlikely, security issue with the Professional version's integrated restoration feature. All Professional users are advised to upgrade. For more information please consult our news article.

Please note that this old release of Akeeba Backup is end of life and no longer supported. This security fix is provided as a courtesy and does not imply that we will provide any kind of support for it.

Please consult our news article.

Additional note: this version also allows the software to run on servers using MySQL 5.6 or later.

Take me to the downloads for this version

Stable 4.0.4

Maturity:
Stable
Released on:
Tuesday, 30 September 2014 03:45
Viewed:
10787 times

This is a regular maintenance release of Akeeba Backup.

Release highlights for this version

Fixed issues with backups on Windows hosts using PHP 5.3. There is a bug on PHP 5.3 on Windows regarding the handling of open files which would cause an error regarding renaming the last part to .JPA when using a non-zero Part Size for Split Archives on a Windows host running PHP 5.3. This version of Akeeba Backup works around the PHP bug. To the best of our knowledge PHP 5.4, 5.5 and 5.6 on Windows, as well as all versions of PHP on Linux and Mac OS X are not affected by this bug.

Important note about RackSpace CloudFiles

Throughout September 2014 and at least until the time of this writing (September 13th, 2014) RackSpace is experiencing severe issues with their API stability. Even though all information you have entered in our software is correct you may get authentication, timeout or upload errors. This is not a bug in our software and we have no control over it. This is an issue with RackSpace and affects all software trying to connect to CloudFiles (e.g. CyberDuck). Moreover, the issues seem to be of an intermittent nature, both regarding time and region. Please do not file support requests and bug reports concerning CloudFiles. We will ignore them until we have determined that CloudFiles works consistently for at least 48 hours straight.

Release highlights for version family 4.0

Resumable backups. If a back-end backup halts with an AJAX error, Akeeba Backup will try resuming it. This allows the backup to complete when it halted due to a temporary network or server issue.

One log per backup attempt. On popular request, a different log file will be created for each backup attempt. This allows you to examine the impact of your configuration changes between backup attempts.

Simultaneous backups. You can now execute several backups at the same time using the front-end, remote JSON API and CLI methods. You are still only able to execute one back-end backup at a time for reasons that have to do with the Joomla! session management and the way browsers work.

Client-side minimum execution time delay. You can now have your browser enforce the minimum execution time preference. This reduces the processor load on the web server, allowing you to take more reliable backups on restrictive shared hosts.

Improved AJAX URL randomisation. The randomisation part of the AJAX action URL has been improved to avoid issues with the security rules of certain hosts. Essentially we will be avoiding cases similar to what happened with GoDaddy in June 2014.

Massive performance boost on large tables. You will observe a massive performance boost when backing up tables larger than a few thousand rows. This might shave up to 85% of the backup time of sites with huge database tables.

Work-arounds for several issues with third party code. We have devised and implemented workarounds for badly written third party code affecting Javascript execution on the page, as well as the badly written error pages of some hosts which contain page-modifying Javascript. Moreover we have worked around the majority of extremely zealous password managers which will auto-fill an irrelevant password into the ANGIE password and/or JPS password fields in the Configuration page without asking you, without letting you know, despite us using the standard autocomplete="off" attribute to let the browser know that it should never auto-fill that field. Our solution is to make the page slower to load and include a lot of delayed Javascript to reset the fields after the browser auto-fills them.

Support for the new MySQL (PDO) driver in Joomla! 3.4. That's right, we support Joomla! 3.4 before it's even released! Akeeba Backup 4.0.0 is designed to support the new MySQL PDO database driver which will be included in the upcoming Joomla! 3.4.0, due for release towards the end of September 2014.

Less hassle. Remember the Post-installation Configuration page you had to go through after each and every installation or update of Akeeba Backup? If you have Joomla! 3.2.0 or later (including 3.3.x and 3.4.x) you will no longer have to put up with it. We are now using the Post-installation Messages component included with Joomla! to display and manage the post-intallation / post-upgrade messages of our component.

Help us get more insight. Our software includes code to anonymously report your PHP, MySQL, Joomla! and Akeeba Backup version. This information cannot be linked to a particular site or person. It will help us get a glimpse at which versions are in use in real world servers, in what relative percentage, and let us to better plan our deprecation strategy. If you don't wish to take part to this anonymous data collection you can opt out from the component's Options page at any time.

PHP 5.3, 5.4, 5.5 or 5.6 is required

This version requires PHP 5.3, 5.4, 5.5 or 5.6. The rationale behind this is explained in our statement of mid-February 2013. It won't install on hosts running PHP 5.2 or earlier. PHP 5.3.4 or later is required, due to show-stopper bugs in earlier versions of PHP 5.3. Important note on reading PHP versions: PHP 5.3.20 is newer than 5.3.10 which is newer than 5.3.4. Moreover, PHP 5.4.0 is newer than PHP 5.3.4.

Due to the necessary Joomla! API changes found only in Joomla! 2.5.6 or later, this version will not install on Joomla! 2.5.5 or earlier versions. In any case, if your server doesn't meet the minimum requirements it will tell you exactly why it cannot be installed (minimum PHP or Joomla! version not satisfied).

Joomla! 2.5, 3.2, 3.3, 3.4 are supported

This version of our software can be installed on Joomla! 2.5.6 or any later 2.5.x release, as well as any 3.2.x, 3.3.x or 3.4.x release. It is not compatible with Joomla! 3.0 or 3.1. These versions of Joomla! are old and vulnerable. If you are using them please upgrade to the latest Joomla! 3 release available from Joomla.org.

Changelog

Critical bugs and important changes

  • [SECURITY: Medium] Possibility of arbitrary file writing while a backup archive is being extracted by the integrated restoration feature

Take me to the downloads for this version