Support

Used Kickstart very often, never a problem, until now:
I did copy the jpa file and kickstart.php tot destination map
Start url.nl/restore.php ( renamed file)

Unpack runs fine, destination map looks OK
After pressing "Run the Installer " I get this error:

Not Found
The requested document was not found on this server.

URL : http://xxxxx.nl/installation/index.php

There is no map " installation" in the destination, not even before pressing the button

Kind Regards,
Jules

Jules,

Please go to the site where you took the backup and check the Configuration for these two fields:

• Backup Type
• Embedded restoration script

Either of them could account for why you don't have an installer available.

Unfortunately, this site is no longer available :-(

rgds,
Jules

Jules,

That isn't good. We're in trouble.

The /installation folder contains two things. First, the script that does the restore. That's easy, we can pull that out of another backup and copy it to the restore site. The second thing is in the /installation/sql folder and that's the database backup. From your description, it appears we have only files in this backup. A "Files only" type of backup would explain what is happening, that's why I asked.

Please double check that you do not have an /installation/sql folder that has been extracted from the archive. You might want to extract it again to make sure it's not just a freak.

Hello Dale,

Yes I am..
I tried extraction of the jpa file on my PC with the Extract Wizzard, but I don't see a map 'installation' but I do see a map SQL, can I use that somehow ?
See attachment



rgds,
Jules

OK, that's VERY good news. What is inside the /sql folder?

a lot of files: (44)
site.s01 until site.site.s043 and site.sql

That's a database dump. But Nicholas says that we never create the sql folder in the root, always in /installation.

What are the dates on those files? Do the .s01, etc. files match the date of the backup?

Yes, they do, but that is because it is the creation date of the unpacking, so they all have the time and date of the unpack.
The contents looks familiar, is there a way to create an installation script, ( take it from another. jpa or so ? )

Yes, I'm working on the installation script, pulling it from another backup.

We're dealing with a broken backup. Is there another backup available? According to Nicholas, that /sql folder should not be in the root. What we're creating is a Frankenstein's monster of a backup to restore your site. This is a path of last resort.

I have daily backup's , I went back to January 1st, but they all have no installation..

I noticed that in the SQL folder the databases.json file is missing, is that crucial ?

The json file contains the default database settings, password, user, etc.

Please post the first five lines of the site.sql file.

CREATE TABLE `#__action_log_config` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `type_title` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `type_alias` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `id_holder` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `title_holder` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `table_name` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `text_prefix` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=20 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
INSERT INTO `#__action_log_config` VALUES ('1', 'article', 'com_content.article', 'id', 'title', '#__content', 'PLG_ACTIONLOG_JOOMLA'), ('2', 'article', 'com_content.form', 'id', 'title', '#__content', 'PLG_ACTIONLOG_JOOMLA'), ('3', 'banner', 'com_banners.banner', 'id', 'name', '#__banners', 'PLG_ACTIONLOG_JOOMLA'), ('4', 'user_note', 'com_users.note', 'id', 'subject', '#__user_notes', 'PLG_ACTIONLOG_JOOMLA'), ('5', 'media', 'com_media.file', '', 'name', '', 'PLG_ACTIONLOG_JOOMLA'), ('6', 'category', 'com_categories.category', 'id', 'title', '#__categories', 'PLG_ACTIONLOG_JOOMLA'), ('7', 'menu', 'com_menus.menu', 'id', 'title', '#__menu_types', 'PLG_ACTIONLOG_JOOMLA'), ('8', 'menu_item', 'com_menus.item', 'id', 'title', '#__menu', 'PLG_ACTIONLOG_JOOMLA'), ('9', 'newsfeed', 'com_newsfeeds.newsfeed', 'id', 'name', '#__newsfeeds', 'PLG_ACTIONLOG_JOOMLA'), ('10', 'link', 'com_redirect.link', 'id', 'old_url', '#__redirect_links', 'PLG_ACTIONLOG_JOOMLA'), ('11', 'tag', 'com_tags.tag', 'id', 'title', '#__tags', 'PLG_ACTIONLOG_JOOMLA'), ('12', 'style', 'com_templates.style', 'id', 'title', '#__template_styles', 'PLG_ACTIONLOG_JOOMLA'), ('13', 'plugin', 'com_plugins.plugin', 'extension_id', 'name', '#__extensions', 'PLG_ACTIONLOG_JOOMLA'), ('14', 'component_config', 'com_config.component', 'extension_id', 'name', '', 'PLG_ACTIONLOG_JOOMLA'), ('15', 'contact', 'com_contact.contact', 'id', 'name', '#__contact_details', 'PLG_ACTIONLOG_JOOMLA'), ('16', 'module', 'com_modules.module', 'id', 'title', '#__modules', 'PLG_ACTIONLOG_JOOMLA'), ('17', 'access_level', 'com_users.level', 'id', 'title', '#__viewlevels', 'PLG_ACTIONLOG_JOOMLA'), ('18', 'banner_client', 'com_banners.client', 'id', 'name', '#__banner_clients', 'PLG_ACTIONLOG_JOOMLA'), ('19', 'application_config', 'com_config.application', '', 'name', '', 'PLG_ACTIONLOG_JOOMLA');
CREATE TABLE `#__action_logs` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `message_language_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `message` text COLLATE utf8mb4_unicode_ci NOT NULL, `log_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `extension` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_id` int(11) NOT NULL DEFAULT '0', `item_id` int(11) NOT NULL DEFAULT '0', `ip_address` varchar(40) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '0.0.0.0', PRIMARY KEY (`id`), KEY `idx_user_id` (`user_id`), KEY `idx_user_id_logdate` (`user_id`,`log_date`), KEY `idx_user_id_extension` (`user_id`,`extension`), KEY `idx_extension_item_id` (`extension`,`item_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE `#__action_logs_extensions` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `extension` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
INSERT INTO `#__action_logs_extensions` VALUES ('1', 'com_banners'), ('2', 'com_cache'), ('3', 'com_categories'), ('4', 'com_config'), ('5', 'com_contact'), ('6', 'com_content'), ('7', 'com_installer'), ('8', 'com_media'), ('9', 'com_menus'), ('10', 'com_messages'), ('11', 'com_modules'), ('12', 'com_newsfeeds'), ('13', 'com_plugins'), ('14', 'com_redirect'), ('15', 'com_tags'), ('16', 'com_templates'), ('17', 'com_users');

Frankenstein it is then!

We can use the emergency restore instructions here since the install script won't work without databases.json.

We know that's an Akeeba Backup database dump from the #__ table prefixes. We still don't know if it is an old one or the current one.

Okay Dale,
Unorthodox, yes. Cross your fingers!
I'll be back..

Jules

Hi Dale,
Restoring te site.sql file does only return the admin tools tables,
What can you tell me about the other files site.s01 until site.site.s043 ?

Jules

All of those files are required. The database dump is in multiple parts. All 43 parts make up the complete database dump.

Hello Dale,

The link you gave me talks about only one file :
"Take a look at the directory where you extracted your backup archive. Inside it there is a directory named installation. Inside this, there is a subdirectory named sql. Inside this there is a file, site.sql (older versions: joomla.sql), containing your database data."

Should I treat all the others like this ? can I concatenate them ?

rgds,
Jules

Jules,

In this case, the s01, etc. files are a part of the SQL file.

You can concatenate them, the only risk is that the file could get too large to import within the PHP time limits. That's why we break it into parts. If it's too big, you can always break it up again. I doubt 43 parts would be necessary.

Hello Dale,

I finally manged to restore the database, using the file in the SQL folder. After find/replace of the SQL commands I imported them one by one.
Thanks for your advice.

The option "Embedded restoration script" was indeed set to NO.
I do not now how this terrible mistake happened, in mho this question makes not much sense, why not always embed the script? I does not harm, does it ?

Regards,
Jules

Jules,

I'm glad it worked out, it looked pretty grim for a while there.

The "No embedded restoration script" doesn't make much sense in Joomla!. But the same code is used in Solo, where it does make sense. If I back up my family tree site using Solo, it makes no sense to put in a restore script because it doesn't know how to restore that software.

Paranoia is your friend. Do a test restore of your backups every once in a while just to make sure that you have a good backup.