There are various ways to replicate Joomla! environments we can use 3rd party tools like XCloner, etc… In this article, I am going to show rather simple way to achieve the replication of Joomla! or any other CMS.
Background: We are replicating server1 to server2
Assumptions: Both servers have Joomla! installed up and running
Step 1 (Server2): Rename configuration.php to configuration.server2
Step 2 (Server1): Backup file system to a *.tar file. We will name it backup_server1_ddmmyyyy.tar
Step 3 (Server1): Backup database of Server1. We will name it db1
Note: You can achieve step 2, and step 3. Using following bash script
Sample Script Link →
Step 4 (Server2): Drop all tables in db2
Note: You can use following sample script for Step 4
Sample Script Link →
Step 5 (Server2): Extract backup_server1_ddmmyyyy.tar (overwrite mode!)
Step 6 (Server2): Restore db1 using db2 connection string
Note: You can use following script for Step 5 and Step 6
Sample Script Link →
Step 7 (Server2): Delete configuration.php
Step 8 (Server2): Rename configuration.server2 to configuration.php
This is one way to replicate or sync to Joomla! websites. There can be many solutions if you know a better tool or way please share.
I have been using Akeeba Backup for more than an year now. Here is my analysis of the product.
- Akeeba backup is wonderful tool if you are want to backup your Joomla! CMS on the fly. This is where I use this tool on daily basis for example, If I am modifying the Joomla! website (i.e. installing component, plugin, module, etc.). I always create a full backup of the Joomla! website before modifying anything and I think this where Akeeba backup is at its best. Akeeba Backup gives administrators to backup up the content and the database on the fly.
- Moving Joomla! site from one hosting to another company. Secondly, I think the most strongest point of the Akeeba Backup Solution is the creation of backup archive (*.jpa). This gives the portability to Joomla! administrator to move or migrate Joomla! website easily and smoothly . Here is the process I follow to move a Joomla! site from one hosting company to another.
– Create a full Joomla! backup using Akeeba backup (Professional)
– Using your FTP client download the *.jpa file
– Upload the *.jpa file to “new” hosting FTP root directory
– Download “Kick Start” from Akeeba Backup official website (Link: https://www.akeebabackup.com/download/official/akeeba-kickstart.html)
– Upload kickstart.php file to “new” hosting FTP root directory
– Run the Kick Start wizard which is very simple. The Kick Start wizard will extract the content from *.jpa file and will guide you through the installation steps. (Knowledge base: https://www.akeebabackup.com/documentation/akeeba-kickstart-documentation.html)
- Don’t just rely on Akeeba Backup. Its a wonderful backup tool but FTP upload configuration has failed on multiple occasions while I was using this product with Akeeba FTP upload configuration. In order to solve the problem, I have created a custom bash script to upload the archive file (*.jpa file) to remote FTP server. I run this script nightly using cron job.
- Large Content Joomla! website and Shared Hosting. Based on my experience I have seen “Internal Server Error” creating a backup for large content website (i.e. 4000+ files). Now, I have experienced this on Godaddy Hosting. I would like to mention the hosting company name as this is very important.
- Updates every month. Akeeba backup as a company updates their extensions every month and with every Joomla! release. I have been monitoring them for an year now. From my experience its little too much of updates; I haven’t ran the diffs between the two updates but I believe the changes will be very minimal. I can understand the security releases are critical but literally they release new version every month. Updates of the product are easy but still another job for Joomla! administrator to watch.
- Cost. I think the cost of the product (i.e. pro version) for yearly subscription is on the higher side, this product cost around $53 USD/year (i.e. 40 EURO/year).
Alternative to Akeeba Backup: There is really one alternative to Akeeba Backup and that is XCloner and its FREE. Link: http://www.xcloner.com/
Disclaimer: This is just a professional review on the Akeeba Backup product. I wish good luck to the developer of the product.