Nobbie wrote:Each site? Or only Joomla & WordPress?
What if have SMF Forum 2.x installed or phpBB3 or Magento or any shop system or or or .... all easily done with Akeeba?
I know Akeeba specificly from Joomla and Wordpress because that are preconfigured modules/plugins nearly each beginner is able to use.
But there is also a component called Akeeba solo which is a more generic approach you can use to backup other scripts too )never used it so i cannot say really much about it).
Nobbie wrote:And what about changes in configuration files (i.e. changes in php.ini, in httpd.conf etc.), and what about code changes due to different server releases (as it is given here for example)?
Which code changes do you mean?
Of course Akeeba is not the holy grail of backup mechanisms at all. It can only backup and restore a script from scripts side of view because it is a webapplication backup script. Any configuration changes needed to be done on the server components or compatibility issues needs to be solved by the user.
But Akeeba makes some things very easy especially for beginners.
You have a single minimalistic interface, you can start a backup with one click and the output will be a single backup file. No need to export your database with phpmyadmin, no need to file transfer 10000 files from the server.
This single file, a Akeeba kickstart file and the new informations for database connection and URL is enough to restore your whole site to a different server.
Nobbie wrote:I think Akeeba may be usefull for a simple server change (but with similar or same infrastructure), which only requires the data and some patches to the WordPress/Joomlay configuration. But it does BY FAR not solve all problem which may arise, when changing the whole infrastructure. Akeeba is only "die halbe Miete" or less.
Thats correct. If you are doing a full backup manually (like "the common way") this checks and adjustments to the new infrastructure needs to be done too.