Joomla | WordPress | Drupal | Prestashop | Magento | Moodle | phpBB
present slides https://slides.woluweb.be
video (FR) YouTube : rJbYrQQlRP4
« An untested backup is as good as no backup at all »
your life !
But it was also streamed in order to remain available 24/7 on YouTube so that everybody can enjoy it virtually ;)
Since then, it has been updated and also presented a.o. at different JoomlaDays :
Look at this presentation at your own risks
This presentation contains no allergens but the (physical/virtual) presence at Joomla events can induce a dependence.
If you feel the symptoms after this presentation, follow instructions :
In this presentation I just share my enthousiasm about a nice solution so that everyone can benefit from my own experience
But note that I am not sponsored in any way by the developer of the mentioned Restoration Tool (all I have is a free sticker )
Like many I just happen to be a happy subscriber of his Backup Tool…
… and his Restoration Tool is available at no extra cost
In a previous presentation I explained in detail “how to secure your automatic backups by transferring them to the cloud on Amazon S3 with Akeeba Backup”
In this presentation, I will explain in detail the next step, namely how to use a script that will automatically
Different cases :
The automated restoration solution works for all the major CMS. The automated upgrade/update is nevertheless specific to Joomla, unless you know of a script that can do that job.
Akeeba Backup for Joomla
Akeeba Backup for WordPress
Akeeba “SOLO” for all other CMS or PHP applications Download https://www.akeebabackup.com/products/akeeba-solo.html Documentation https://www.akeebabackup.com/documentation/akeeba-solo.html
To quote the site :
“A command-line application created for power users. Automatically restore one or multiple sites. Useful for mass site creation or maintaining demo sites. Exclusively available to AKEEBABACKUP, BACKUPWP, SOLOPHP, ESSENTIALS and JOOMLADELUXE subscribers.”
Let’s suppose you manage plenty of websites.
As you know, you should definitely check the integrity & completeness of your backups on a regular basis.
Besides this, before upgrading Joomla and updating all extensions, you would like to be sure that everything will be OK.
Last, now that it becomes so easy to restore/upgrade/update all your sites, you will be very happy to test the future Beta and Release Candidate releases of Joomla and to contribute !
Let’s see how to automate the whole process very easily.
One double-click on a script and all your sites are restored/upgraded/updated.
See the “exciting” video of the script doing your work on the next slide (1m32s for 2 sites in this example).
All you need to do after is to check on your local server if all websites are fine…
First of all, please RTFM :) Everything is explained in detail in the following official documentation https://www.akeebabackup.com/documentation/unite/
Download Akeeba UNiTE and unzip it on your local server. For this presentation, I have uncompressed it in a folder named
My local server being Xampp for Windows, the root is
C:\xampp\htdocs and so here is the complete path in my case :
For every site, create an XML file that you typically put in the same folder as Akeeba UNiTE.
You could create a subfolder of course.
Note that before version 4.x of Akeeba UNiTe, the XML files were typically in a
<?xml version="1.0" encoding="UTF-8"?> <unite scripting="02_angie"> <siteInfo> <package>/demo_backups/1demo.jpa</package> <deletePackage>0</deletePackage> <localLog>test.log</localLog> <emailSysop>0</emailSysop> <name>Restored with Akeeba Unite</name> <email>email@example.com</email> <absolutepath>C:\xampp\htdocs\akeeba_unite_output\1demo</absolutepath> <adminID>79</adminID> <adminUser>admin</adminUser> <adminEmail>firstname.lastname@example.org</adminEmail> <adminPassword><![CDATA[admin]]></adminPassword> <force_ssl>0</force_ssl> <removephpini>1</removephpini> <removehtpasswd>1</removehtpasswd> <replacehtaccess>1</replacehtaccess> </siteInfo> <databaseInfo> <database name="site"> <changecollation>0</changecollation> <dbdriver>mysqli</dbdriver> <dbhost>localhost</dbhost> <dbuser>root</dbuser> <dbpass></dbpass> <dbname>1demo</dbname> <dbprefix>test_</dbprefix> <existing>drop</existing> <foreignkey>1</foreignkey> <noautovalue>1</noautovalue> <replace>0</replace> <utf8db>0</utf8db> <utf8tables>0</utf8tables> <utf8mb4>0</utf8mb4> </database> </databaseInfo> </unite>
<?xml version="1.0" encoding="UTF-8"?> <unite scripting="02_angie"> <s3> <accesskey>ABCDEF</accesskey> <secretkey>123456</secretkey> <signature>v4</signature> <bucket>mybucket</bucket> <region>eu-central-1</region> <ssl>1</ssl> <filename>path/to/site-backup.jpa</filename> </s3> <siteInfo> <package from="s3"></package> <deletePackage>0</deletePackage> <localLog>test.log</localLog> <emailSysop>0</emailSysop> <name>Restored with Akeeba Unite</name> <email>email@example.com</email> <absolutepath>C:\xampp\htdocs\akeeba_unite_output\3demo-amazons3</absolutepath> <adminID>79</adminID> <adminUser>admin</adminUser> <adminEmail>firstname.lastname@example.org</adminEmail> <adminPassword><![CDATA[admin]]></adminPassword> <force_ssl>0</force_ssl> <removephpini>1</removephpini> <removehtpasswd>1</removehtpasswd> <replacehtaccess>1</replacehtaccess> </siteInfo> <databaseInfo> <database name="site"> <changecollation>0</changecollation> <dbdriver>mysqli</dbdriver> <dbhost>localhost</dbhost> <dbuser>root</dbuser> <dbpass></dbpass> <dbname>3demo</dbname> <dbprefix>test_</dbprefix> <existing>drop</existing> <foreignkey>1</foreignkey> <noautovalue>1</noautovalue> <replace>0</replace> <utf8db>0</utf8db> <utf8tables>0</utf8tables> <utf8mb4>0</utf8mb4> </database> </databaseInfo> </unite>
When I discovered Akeeba UNiTE, the restoration directly from Amazon S3 was already present, but only with signature v2. Therefore, the tool would not be able to access my backups, which are stored in EU (Frankfurt) and use v4.
Following an exchange with Nicholas, again he upgraded UNiTE and amended the Documentation to integrate Amazon S3 v4 !
Txs Nicholas :)
In particular, a new parameter is now needed, ie the Region
For more information, see
The principle for restoration is very simple : simply execute the following command from the Akeeba UNiTE folder on your local server
Note : before version 4.x released in 2018, the command was
Advantage of the new phar format introduced in version 4.x of Akeeba UNiTE: everything is in 1 file :)
Note : before version 4, the XML files were by default in a subfolder called '''inbox’''
But anyway you are of course free to place your xml files whereever you want. Example from the Manual :
/usr/bin/php-cli /path/to/unite.phar /home/myuser/backups/mysite.xml
If you are a Linux user, no doubt you don’t need my/any help to run the script
If you are a Mac user, macOS comes with PHP pre-installed.
So you just need to do php ./unite.phar mywebsite.xml
Paradoxically, on a live server running Unix at my hosting companies I knew how to use the Command Line… but on my Windows local server I had no clue :) So here the answer :
Search and launch CMD (the Command Line)
Go to the PHP directory of your local server. In my case
mywebsite.xmlbeing in the same folder as
php C:\xampp\htdocs\akeeba_unite\unite.phar mywebsite.xml
Of course, when you have many website to restore, you want to create a Batch file in order to process all your websites in one double-click
.batfile, for example in
There is a script out there allowing to upgrade Joomla and update its extensions from the Command Line. It is a proof of concept so
and put that file in the same folder as '''unite.phar’'' NB: afterwards we will copy this file on each restored website in order to be executed, see hereafter
But please be aware that
update.php should not be used on Production sites, as it has drawbacks :
See for example https://github.com/joomla-projects/cli-update/issues/1
Also, read here the feedback by Nicholas : I had written the same kind of script. Eh, I wouldn’t recommend updating Joomla! from CLI. The last bit which cleans up old files is still a hit and miss and we’ve only been able to make it work through the web interface. We being Michael Babker, George Wilson and yours truly. The update is based on Akeeba Restore which is also the heart of Kickstart, UNiTE and the integrated restoration feature in my backup software. The trick is that we have a post-extraction script which loads a thin layer of Joomla! to execute the post-update tasks. This needs to load the NEW version of Joomla! you have just installed. When running from CLI you end up with some of the loaded classes being from the PREVIOUSLY installed version of Joomla! which can make things go boom.
NB : see the future of CLI update here:
The full Batch file is detailed in 2 versions on the next 2 slides (Windows example), but here are the key commands/steps :
Restore the website
php unite.phar 1demo.xml
Copy the update script into the CLI folder of the website
copy "C:\xampp\htdocs\akeeba_unite\update.php" "C:\xampp\htdocs\akeeba_unite_output\1demo\cli\update.php"
php C:\xampp\htdocs\akeeba_unite_output\1demo\cli\update.php --extensions php C:\xampp\htdocs\akeeba_unite_output\1demo\cli\update.php --core
REM This Script (i) automates installation of backups (ii) upgrades Joomla (iii) updates all extensions set STARTTIME=%TIME% REM Needed for Windows: adds the folder containing php.exe to the path (Xampp being here the Local Server) PATH=%PATH%;C:\xampp\php REM Change Directory to the folder containing your script CD C:\xampp\htdocs\akeeba_unite\ REM Restore all websites php unite.phar 1demo.xml php unite.phar 2demo.xml REM Copy the update.php script in the CLI folder of each website copy "C:\xampp\htdocs\akeeba_unite\update.php" "C:\xampp\htdocs\akeeba_unite_output\1demo\cli\update.php" copy "C:\xampp\htdocs\akeeba_unite\update.php" "C:\xampp\htdocs\akeeba_unite_output\2demo\cli\update.php" REM Update all extensions php C:\xampp\htdocs\akeeba_unite_output\1demo\cli\update.php --extensions php C:\xampp\htdocs\akeeba_unite_output\2demo\cli\update.php --extensions REM Upgrade Joomla php C:\xampp\htdocs\akeeba_unite_output\1demo\cli\update.php --core php C:\xampp\htdocs\akeeba_unite_output\2demo\cli\update.php --core echo Start Time : %STARTTIME% echo End Time : %time% pause
REM This Script (i) automates installation of backups (ii) upgrades Joomla (iii) updates all extensions set STARTTIME=%TIME% REM Needed for Windows: adds the folder containing php.exe to the path (Xampp being here the Local Server) PATH=%PATH%;C:\xampp\php REM Change Directory to the folder containing your script CD C:\xampp\htdocs\akeeba_unite\ for %%x in (1demo 2demo 3demo 4demo) do ( REM Restore backup php unite.phar %%x.xml REM Copy the update.php script in the CLI folder of each website copy "C:\xampp\htdocs\akeeba_unite\update.php" "C:\xampp\htdocs\akeeba_unite_output\%%x\cli\update.php" REM Update all extensions php C:\xampp\htdocs\amazons3\%%x\cli\update.php --extensions REM Upgrade Joomla php C:\xampp\htdocs\amazons3\%%x\cli\update.php --core ) echo Start Time : %STARTTIME% echo End Time : %time% pause
If you restore many websites, after the script has run you might want to copy-paste the contents of your Command Line window to your favourite Notepad.
That way, you can quickly check whether all restorations (and updates/upgrades) went fine.
NB : the script show the Start Time and End Time. This is of course optional. In my case, each restore takes on average less than 1 minute.
Note : you can even create a SQL file to suit you own needs and point to it in your XML file in UNiTE
That’s BTW how you can automate everything with UNiTE, for example
Your website forces SSL (https) but your local server does not handle https ?
5 alternative solutions :
<force_ssl>0</force_ssl>parameter that you can put in your XML file
If the configuration.php is not part of the backup, the automatic restoration will not work (although a manual restoration with Akeeba would work !).
So be sure that configuration.php is part of your backup…
If you use Memcache on your live site, the locally restored website will not work.
Simply edit configuration.php and change the
$cache_handler as follows :
$cache_handler = 'file'
More generally about anything related to configuration.php :
If you are restoring the same site on your local / demo / dev / whatever server all the time you can create a small ZIP file with a prefabricated configuration.php file and have UNiTE extract it to the site’s root.
That’s what Nicholas himself does with his continuous restoration of my live site’s backups to my local server :)
When you check your sites, you get redirected from
You probably left the original .htaccess file forcing
Just delete it and replace it by the native .htaccess file
Even better : use the option in the XML file allowing to automate it !
Another cause can be some “conflict” with your antivirus software.
Example from a forum :
“My Avast ! Free Antivirus redirects localhost:8080 to www.localhost.com:8080. I reset the web redirection setting in Avast!”
If you use SiteGround’s Cache Plugin, you might get an error message on the front-end of your website.
Simply disable that plugin from the backend in order to test your site effectively.
You can also automate this by creating a SQL file that disable misbehaving plugins and point to it in your XML file in UNiTE.
Your process freezes in the middle of the restore phase ?
Just delete the stealth .htaccess file and finish the installation manually (
You see no images on your local website ? You probably left the original .htaccess file. Just delete it and replace it by the native .htaccess file
Even better : use the option in the XML file allowing to automate it !
In the case of two websites “sharing some tables” (like the Users table) with a View, the restoration would not work for the website having the View instead of the Table.
The XML file allows to change the Name of the site.
Well, for multilingual sites, if you have setup a different Name for some language, of course this is left as it is.
So if you really need to have that changed as well, you can also play with Akeeba UNiTE in order to run some SQL query automatically.
Well, there could be many reasons to that one. But what I have experienced from a couple of sites is that there were some files with special character at the root of the original website, like
(even though that question mark had never caused me any issue during manual backup/restore !)
This issue has in fact nothing to do in itself with Akeeba UNiTE, but when you restore a website having an Acymailing module on the front-end, typically the page will throw a popup telling that “localhost is not allowed”.
In order to fix that, go to
Acymailing > Configuration > Subscription > Allowed domains for the redirection via the module
|localhost to the field
Actually you don’t even have to download your backups in the first place.
In your XML file, you can directly specify your credentials.
This can be done with the following Tag for Amazon S3 : https://www.akeebabackup.com/documentation/unite/using.html#xml-s3
Or with the following Tag if you connect directly to your website : https://www.akeebabackup.com/documentation/unite/using.html#xml-remote
The disadvantage : you have to edit each XML file to adapt for the name of the backup file because (unless you configure it otherwise) the latter typically contains a timestamp.
To download all your backups from Amazon S3, use for example Cyberduck
NB : contrary to other softwares like FileZilla, Cyberduck can indeed login to AS3
(Or download them from each website, but that will take much more time…)
Well, if your backups are already available for example on the local server where you want to restore them all, no need to download them.
In Options 2 and 3, your backups are on your local server. But as already mentionned for Option 1, the name of the backup files typically contain a timestamp.
One could of course simply adapt each XML file accordingly everytime.
But I guess a better solution is to first rename the backup files manually.
An even more efficient solution is to rename the backup files automatically.
Using Windows, this can be done for example with a tool like Bulk Rename Utility : http://www.bulkrenameutility.co.uk/Download.php
In my case, I remove the first 9 characters (site-www.) and the last 16 characters (timestamp of the backup) :
As suggested by Nicholas, you can even automate the whole process (download from AS3/rename/restore) with shell scripts.
With other words, a kind of mix of all previous Options :
FYI that bit works perfectly on a Raspberry Pi 2, a really underpowered ARM thingie with barely 512M RAM.
I’m not sure I would need that, but on Windows you could use the Task Scheduler in order to launch the restoration of all backups automatically at regular intervals.
But this would of course first require to also automate the Download of the backups.
If you want to test your websites further, you might want to install a MailCatcher. That way, you can also simulate the sending of a newsletter, the transactional emails etc.
See for example http://nilhcem.com/FakeSMTP
Arkiv is an easy-to-use backup and archive tool.
Arkiv is designed to backup local files and MySQL databases, and archive them on Amazon S3 and Amazon Glacier. Backup files are removed (locally and from Amazon S3) after defined delays.
Arkiv could backup your data on a daily or an hourly basis (you can choose which day and/or which hours it will be launched). It is written in pure shell, so it can be used on any Unix/Linux machine.
Control, repair or convert your zip, jpa, rar files
Presentation in French :
Someone has kindly told me about another solution to backup/restore/upgrade websites.
I haven’t tested it, but feel free to see what it can do for yourself :
I discovered the existence of update.php in an excellent presentation made by Andy Gaskell at #jd17uk
for even more interesting DevOps tools :)
The previous episode was about automating backups in the cloud
The present episode is about automating restoration (and updates/upgrades) on your local server
In the next episode, why would you not do the final step and learn how to become a Joomla Tester ?
The project (published on 2 June 2018)
The aim of this project is to add a good CLI Application to the Joomla! CMS, that can perform the updates without going to the administrative panel. Administrators can just go via SSH to update somethings within the CMS.
The idea for it to be core feature in Joomla! 4. See the code here : https://github.com/joomla-projects/gsoc18_cli_update
Watch the video (FR) : YouTube : rJbYrQQlRP4
Any suggestion about this presentation ?
Please feel free to contact me. I’ll be happy to keep improving it :)
Marc Dechèvre | @woluweb
+32 474 37 13 12 | +32 2 772 58 69