A typical backup/restoration work flow


If you are looking for a quick start to using the component please watch our video tutorials.

Akeeba Backup is designed to make backing up and restoring a site easier and more user-friendly. From Akeeba Backup's perspective, restoring to the same host and location, copying your site in a subdirectory / subdomain of the same host or transferring your site to a completely new host is exactly the same. In short, Akeeba Backup doesn't care if you are restoring, copying, cloning or migrating your site. The process is always the same; you only have to learn it once. The learning curve is quite smooth, too!

Please note that only MySQL-compatible database servers are supported (e.g. MySQL, MariaDB, Percona). You cannot take a backup of Joomla running on PostgreSQL or restore a backup of a site on a server that only has a PostgreSQL database. Also note that some MySQL-compatible servers may have slight incompatibilities between them. When transferring a backup across database servers we attempt to account for these incompatibilities. If something doesn't work, please let us knwo.

The typical work flow involves using two utilities from the Akeeba Backup suite: the Akeeba Backup component itself, and Akeeba Kickstart (our archive extraction helper). Here is the overview:

  1. Install Akeeba Backup and configure it to taste. Or use the automated Configuration Wizard to automatically configure it with the most suitable settings for your server. Hit on the Backup Now button and let your site back up. When it finishes up, click on the Manage Backups button. Click on the download links on the far-right of the only backup entry from the list - or, better yet, use FTP to do that - saving all parts of the backup archive somewhere on your local PC.

  2. Extract the kickstart-VERSION.zip file you downloaded from our Downloads page. The only files in there are kickstart.php and the translation INI file. Upload them to the server on which you want to restore your site to.

  3. Upload all parts of the backup archive (do not extract it yet, just upload the files) to the server on which you want to restore your site to (called here forth the target server ). Your server's directory should now contain the kickstart.php and the parts of the backup archive (.jpa, .j01, etc).

  4. Fire up your browser and visit the Kickstart URL on your target server, for example http://www.example.com/kickstart.php .

  5. Change any option - if necessary - and hit the Start button. Sit back while Kickstart extracts the backup archive directly on the server! It's fast too (when compared to FTP uploading all those 4000+ files!). If it fails with an error, go back, select the Upload using FTP option and supply your FTP connection information, then click on Start again.

  6. A new window pops up. It's the restoration script called ANGIE. This was placed in your backup archive when you took the backup. It's used to restore the database and do any site reconfiguration actions necessary at the end of the restoration. Do not close the Kickstart window yet!

  7. Follow the prompts on your screen, filling in the details of the new server. If you are restoring to a different URL or server than where the original site was backed up from you will need the database connection information. If unsure about what this information is please ask your host.

  8. When ANGIE is done restoring your site it prompts you to close the window / tab it was running in. Go ahead and do it.

  9. Back to the Kickstart window, click the button titled Clean Up. Kickstart removes the installation directory, restores your .htaccess file (if you had one in the first place), removes the backup archive and itself.

  10. Click on the View the front-end button to visit your new site. You're done.

If you are restoring to a different subdirectory on the same server as the original site, or to a whole different host, you might need to rename or edit your .htaccess file for your site to work properly. ANGIE does give you an option to do either of these actions for you, in the Site Setup page.

Also note that some third party extensions which store absolute filesystem paths, absolute URLs or contain host- or directory-specific settings may require manual reconfiguration after the restoration is complete. This is all described in the restoration section of this guide. If you need help backing up your site, take a look in the Backup Now section of this guide.

Can I restore the backup archive manually?

Yes, you can do that in an emergency. You should not do that to do a normal restoration, despite what ChatGPT, Bing Chat, or whichever “Artificial Intelligence” tells you (they are not intelligent; they are a glorified version of your phone's text autocomplete, they make glaring mistakes, and they deliver them with the unmistakable overconfidence of the village idiot). Under normal circumstances, you are supposed to use the restoration script included in the backup archive as explained above.

If and only if you cannot access the restoration script, e.g. if you are trying to restore a backup archive with a version of our software which predates your PHP version, you can use the Emergency Restoration Procedure documentation page for more information.

Please note that you should only use this method in an actual emergency. If you want to restore only some files included in the backup archive use the Files to extract feature in Akeeba Kickstart. If you want to only restore a few of the database tables, you can do so with the restoration script included in the backup archive, using the Tables to restore feature in the database restoration page.