Support

I’d like to remind you that Akeeba Kickstart’s role is solely to extract the backup archive – it does not perform a full site restoration. The current version, Kickstart 8.0.6, works perfectly with backup archives created by Akeeba Backup for Joomla 10.0.5. In the month since the release of Backup 10.0.5, I have personally used Kickstart 8.0.6 to move dozens of sites across several development and testing environments, and even to restore a live site without issues.

To help us pinpoint the problem you’re experiencing, could you please share a little more detail? Specifically:

• What exact steps you are following when you run Kickstart.
• Any error messages or warnings that appear, and the exact wording of those messages.
• Whether the issue occurs during extraction, after extraction (e.g. when using the Backup Restoration Script), or at another stage.

With that information we’ll be able to guide you more effectively and get your site back on track.

Looking forward to your reply.

You probably have a malformed table name in the backup. Try disabling "Stop on CREATE error" and "Stop on other error" in the Database Restoration page.

Please upload a copy of your backup archive file(s) to Dropbox, OneDrive, Google Drive or something similar. In your next reply please paste a public share link (not password protected or requiring authorization) so I can try to restore it locally and tell you what is going on.

You have a pretty messed up database, but we can work around that.

After extracting the backup archive and before pressing the "Run the installer" do the following.

Edit the following files under the installation/sql directory:

• site.sql
• site.s05
• site.s06
• site.s16
• site.s27
• site.s59

In each file replace the following (some files may only have one instance of one replacement, others may have multiple instances of either or both replacements; make sure to replace all instances of the following replacements):

• ``#__content`- with `#__content-
• ``#__categories`- with `#__categories-

Go back to Kickstart and click on the "Run the installer" button.

When you are in the Database Restoration page, look at the right hand pane. Enable the "Select which database items to restore" option. A new area opens below.

Click on Add All to select all entries. Then, deselect the following items by CTRL-clicking the following entries:

• #__categories-DaSi-20250729-2153(orig)
• #__categories-DaSi-20250730-1534
• #__categories-DaSi-20250731-1711
• #__categories-DaSi-20250731-2337
• #__categories-DaSi-20250731-2346
• #__categories_Dasi-20250801
• #__categories_copy
• #__categories_test
• #__content-DaSi-20250729-2153
• #__content-DaSi-20250729-2210
• #__content-DaSi-20250730-1534
• #__content-DaSi-20250731-1704
• #__content-DaSi-20250731-1711
• #__content-DaSi-20250731-2337
• #__content-DaSi-20250731-2346

Then proceed as normal. Your site will restore just fine.

I would like to point out two things.

First, DO NOT try to create copies of core Joomla tables such as #__categories and #__content. It won't work. Joomla also creates corresponding entries in the #__assets table, but this table's entries cannot be managed by hand, and are tied to everything in Joomla – including installed extensions. Copying core tables around is at best useless. If you try restoring them (renaming them back) it's worse than that; it breaks your site in subtle ways which make it misbehave, break core and third party extensions, and break Joomla core updates. 100% of the update issues I have ever seen are, in fact, caused by someone doing table juggling like you did. While this kind of database abuse worked perfectly fine in Joomla 1.0 (which became EOL in 2007) and to some extent in Joomla 1.5 (which because EOL in 2012) it has not worked since Joomla 1.6!

Second, DO NOT use anything other than lowercase Latin letters without accents or diacritics (a-z), numbers, underscores, and dashes in database table names. Other characters may or may not work. Most definitely DO NOT use backticks (`), single quotes (') or double quotes (")! These characters have special meanings in MySQL. Including them in a database table name does cause a certain amount of problems in database management software. We try to work around these issues but some cases, like yours, cannot be fully addressed without breaking the behaviour in other, more frequent use cases.

I hope that helps.

Thank you very much! I will be making this ticket public.

Have a fantastic week!