Much improved FTP functions for uploading backup archives and transferring sites. The initial directory is now interpreted more loosely, similarly to what many FTP client software does. If left blank, the directory will be understood as relative to whichever default directory you get when connecting into FTP instead of the absolute filesystem root — but note that this is not recommended as changing the configuration of your FTP server may cause problems with downloading your backup archives and enforcing remote quotas! FTP copying is also improved, taking placing directly at the FTP server side isntead of requiring downloading and reuploading the file. Further to that, the FTP features now support usernames which look like emails (e.g.
) without complaining that the username or password is incorrect. Finally, the FTP methods going through cURL no longer fail if your site miscommunicates to our software that it has a proxy configuration when it really doesn't.
Upload to Azure BLOB Storage now supports chunked uploads, files up to 190.7TB (up from 64Mb). We went back to the drawing board and reimplemented the Upload to Azure BLOB Storage code using the newest version of the Azure BLOB Storage API (version 2019-12-12) which allows individual files uploaded as a single chunk to be up to 5000MiB (up from 64MiB), the maximum chunk size to be 4000MiB (up from 4MiB) and the maximum chunk uploaded file size to be 190.7TiB (up from 3.05GiB). Note that the actual maximum file limit for chunked uploads is 50,000 times the chunk size, therefore if you are using a chunk size of 10MiB your maximum upload file size is 50,000 x 10MiB = 488.28GiB which is still plenty enough for most practical use cases!
OneDrive for Business: you can now use Drives other than your personal. Previous versions of our backup software from late 2019 onwards allowed you to use OneDrive accounts registered through a school or organisation. However, there was a catch: you could only use your personal Drive. You did not have access to any other drives you were allowed access to by your group. In this version of our software we allow you to use any Drive you have access to. If you do not change the configuration then you will still be using the default (personal) drive for your Microsoft account.
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Do not use Akeeba Backup 8 to take backups of Joomla 4 sites. Akeeba Backup 8 is minimally compatible with Joomla 4, as in: it won't break your site when you upgrade from Joomla 3.10 to Joomla 4. The minimal compatibility is there only for the purpose of facilitating the upgrade process from 3.10 to 4.x. You cannot even install Akeeba Backup 8 on Joomla 4.1 and later — this is deliberate, there's no need for you to do that. Once you install Joomla 4 you MUST install Akeeba Backup 9 and complete the migration process to it, then uninstall Akeeba Backup 8 per the messages which will be displayed on Akeeba Backup's Control Panel page. Please note that we do not provide any support for taking or restoring backups of Joomla 4 sites with Akeeba Backup 8 after February 17th, 2022.
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.