07 December 2011 Last updated on 16 January 2012

Akeeba Backup 3.3.11 just released.

We are pleased to announce the immediate availability of Akeeba Backup 3.3.11, a bugfix release.

Akeeba Backup 3.3.11 fixes some minor issues discovered in the 3.3.10 stable release and introduces compatibility with Joomla! 2.5, the upcoming long term support release of the Joomla! CMS.

Getting Akeeba Backup and receiving support

As always, you can download the free version, Akeeba Backup Core, from our Downloads page without any charge. If you are a Professional subscriber you can download the Akeeba Backup Professional release from the same page; just make sure you are logged in before visiting the download page. Alternatively, you can use the integrated Live Update feature of our software to update it automatically on supported server environments.

Since July 7th, 2011, support is provided only to subscribers. We have created a cheap (7.79€) subscription, FORUMACCESS, which gives you access to our Support Forum for eight days, with the same priority as all subscribers to any subscription level. If you already have an active AKEEBAPRO subscription you already have access to the support forum; you don’t need to buy an extra subscription. Moreover, if you have an active AKEEBADELUXE or SUPPORT subscritpion, you can get top priority, confidential support through our Private Ticket support system.

Do you want the best backup solution for Joomla! without spending a fortune? Akeeba Backup Professional can do that, with a flat cost of 40 Euros – or just 30, if you bought an ATPRO subscription the last three moths. An AKEEBAPRO subscription allows you to use the component on as many sites as you want, for as long as you want (even after your subscription expires) and receive updates and support for a whole year. For the price of a dinner for two you can get the best backup solution all your Joomla! 1.5, 1.7 and 2.5 sites. Go Professional today!

Supported versions

Our support policy is to provide support only to the latest published stable release of Akeeba Backup, as well as to the latest published preview (alpha, beta or release candidate) release, if one is available.

Moreover, we only support the Joomla! versions officially supported by the Joomla! project. Due to the plethora of active Joomla! versions, we have consolidated the support terms for different Akeeba Backup and Joomla! version combinations in the table below: 

 

J! 1.5

J! 1.6

J! 1.7

J! 2.5

AB 3.3.11 *

Until April 1st, 2012

Not supported

Until February 15th, 2012

Until August 2013 **

Older releases

No longer supported 

* Only the latest Akeeba Backup 3.3.x release is supported.

** If a new Akeeba Backup series (i.e. 3.4) is released before August 2013, Akeeba Backup 3.3.x will cease being supported, per our support policy stated above.

Please note that Akeeba Backup 3.3.x requires PHP 5.2.7 or later to work. If you have an earlier version of PHP, please ask your host to upgrade it immediately. PHP 4, 5.0, 5.1 and 5.2 are end-of-life products, abandoned over a year ago by their developers, containing known security vulnerabilities. If you are stuck on a host using PHP 5.1.6 up to and including PHP 5.2.6, you can use the (unsupported) Akeeba Backup 3.2.7 release to back your site up in order to move it to a host with up-to-date software.

Changelog

New features

  • Support for Amazon S3 RRS (Reduced Redundancy Storage)

Miscellaneous changes

  • Updating the CLI platform with the new location of Joomla! 2.5's version.php file
  • ABI: Warning message when Javascript is disabled during restoration

High-priority fixes

  • Joomla! 2.5 requires passing the table prefix in getTable()

Bug fixes

  • The header in Administer Backup Files would change when using the pagination controls (thank you @brianteeman)
  • A "Transfer Archive ()" link would appear even when there was no post-processing engine available (thank you @brianteeman)
  • DropBox file operations (delete, download) were not working
  • ABI: The configuration.php would show broken characters when non-ASCII characters were used in any field, e.g. site name or off-line message (kudos to Alexandros S. for the heads up)
  • 311: Intermediate backup files are not removed after backup failure