Restoration: ANGIE now applies very high memory and execution time limits to prevent some timeout / memory outage issues on most hosts. ANGIE will now try to set a maximum memory usage of 1Gb and a PHP execution time limit of one day — much more than it will possibly need. This allows it to work even on slow hosts with unreasonably low default memory and execution time limits, especially during long running operations such as restoring your database. Note that the backup engine typically uses 12 to 16Mb and PHP does NOT reserve the entire memory limit; this is a limit to how much memory can be reserved as needed at a maximum, therefore this option is safe to use even on hosts with much less available system memory e.g. 512Mb or even lower. Likewise, the high timeout limit doesn't mean that ANGIE will run for an entire day or that even trying to do so would necessarily succeed. It's just a limit, i.e. the longest it could possibly run before PHP itself terminates the process.
Restoration: ANGIE now warns you if you leave the database connection information empty. When restoring your site on a different server, domain, subdomain or subdirectory than where you backed up from the default behaviour is to see the database connection information fields empty. This is a good hint that you need to provide connection details to a new database. A stark minority of users left that empty, clicked on the Next button and was promptly perplexed as to why they got an error that they cannot connect to the database. There's a new message in this case notifying the user that they are leaving these fields empty, asking them to confirm this is what they really intended to do. Beyond that there's nothing more we can do to point out the obvious...
Option to set a really large PHP memory limit during backup. Enabling this new option will have the backup engine attempt to set the PHP memory limit to 1Gb. This will allow you to process much larger files on most hosts with very conservative memory limit settings. Note that the backup engine typically uses 12 to 16Mb and PHP does NOT reserve the entire memory limit; this is a limit to how much memory can be reserved as needed at a maximum, therefore this option is safe to use even on hosts with much less available system memory e.g. 512Mb or even lower.
Workarounds for issues introduced by Joomla 4.1.1/4.1.2. A few things changed under the hood in Joomla 4.1.1, including the way the anti-CSRF token checks are performed. Unfortunately, this major change was introduced without prior warning or proper communication from the Joomla! Project in Joomla! 4.1.1. This caused a few issues, notably the Configure and Export buttons in the backup profiles manager do not work anymore. This version addresses these issues.
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Akeeba Backup version 9 will only run on Joomla 4. If you still have a Joomla 3 site, don't worry! Akeeba Backup 8 will still be maintained and receive support from the release of Joomla 3.10 on August 17th, 2021 up to August 17th, 2023. Do note that Akeeba Backup 8 will no longer receive major new features. These will only be implemented on Akeeba Backup 9.
Also note that starting August 17th, 2021 we no longer support Akeeba Backup 8 on Joomla except for the use case of upgrading from Joomla 3 and with the sole intent of updating it to Akeeba Backup 9.
Please consult our Compatibility page. It explains our version support policy and lists which versions of our software are compatible with which versions of Joomla and PHP.