Separate remote and local quota settings. By popular demand, quota settings – how many backup archives to keep – are now separately configured for remote and local backups. This allows you to fine-tune how many backup archives to keep on your local server for immediate restoration without affecting how many backup archives are kept in longer term, remote storage for safekeeping and regulatory compliance. Yes, this means that you can now set up your backups to not delete the backup archive immediately after uploading it to remote storage, and simply set up local quotas to only keep a few of those backups on your web server for easier restoration.
Expert options for the Upload to Amazon S3 configuration. While our integration with the S3 API works great with Amazon S3 proper and some of the most well-known S3-compatible services (such as Google Storqage, Wasabi, etc) out of the box, this is not necessarily true for some lesser-known, third party, S3-compatible services which have a looser interpretation of the S3 API than Amazon's documentation really intended. We now expose a number of fine-tuning options which allow you to change the way our S3 integration works to achieve compatibility even with the more finicky of S3-compatible services out there.
Upload to OneDrive (app-specific folder). This is the third OneDrive integration we offer, one which only allows you to put files into the Apps/Akeeba Backup folder of your drive. While it sounds more limiting, it is less prone to internal authentication errors on Microsoft's side which are outside our control.
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.