Support

Akeeba Backup for Joomla!

#17885 Database Restoration error

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by user63935 on Friday, 18 October 2013 12:34 CDT

user63935
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.11
PHP version: 5.3.27
MySQL version: 5.5.33-31.1
Host: hostgator
Akeeba Backup version: Akeeba Backup Core 3.7.6

Log: http://citieswestsites.com/CWPBULog.txt

Description of my issue: I tried restoring my site after a backup and am receiving a Database Restoration error. I tried several times, but kept getting the error.

I didn't copy the error, and I don't want to go through the process again unless asked (just in case I'm making things worse).

I selected proceed without restoration and now the site comes up fine, but a bunch of articles aren't working and sometimes Joomla adds &Itemid= to the end of urls causing pages not to load properly.

The reason I wanted to restore is completely unrelated to these current issues.

citieswestsites.com

Thanks for your help...

dlb
You have a partial databse restoration or nothing would be there. For the articles that do show on the restored site, is the beginning there, but the end is missing? Does your site use English or another language? Is citieswestsites.com the partially restored site?

I want Nicholas to look at this, it may relate to a database backup bug recently fixed.

Dale


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user63935
You have a partial databse restoration or nothing would be there.

Perhaps, but the missing articles are in the backend. As far as I can tell, everything is there. It's like the menus items or itemIDs got screwed up and nothing is linking properly.

For the articles that do show on the restored site, is the beginning there, but the end is missing?

The articles appear to be whole. Nothing missing from them that I can see.

Does your site use English or another language?

English only.

Is citieswestsites.com the partially restored site?

Yes. citieswestsites.com is the site I'm referencing

Thank you for looking.

dlb
It is not the bug I was thinking of. That's a good thing. I'm still not sure what to do with the error and the menus and itemIDs. I'll leave this flagged for Nicholas.

Dale


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user63935
Cool. Thank you for looking.

nicholas
Akeeba Staff
Manager
I need the exact database restoration error message. Without it it's impossible to say what happened.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user63935
Ok, I re-ran kickstart and got the error again:

An error occurred while restoring the database. The error message can be found below. Click on the × button at the top right of this dialog message to close it and return to the database restoration page.

Database error processing line 103
Database server error reply:

SQL=CREATE TABLE `pm_rokgallery_file_loves` ( `file_id` int(10) unsigned NOT NULL DEFAULT '0', `kount` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`file_id`), UNIQUE KEY `file_id` (`file_id`), CONSTRAINT `pm_file_loves_file_id_files_id` FOREIGN KEY (`file_id`) REFERENCES `bak_rokgallery_files` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8

CREATE TABLE `#__rokgallery_file_loves` ( `file_id` int(10) unsigned NOT NULL DEFAULT '0', `kount` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`file_id`), UNIQUE KEY `file_id` (`file_id`), CONSTRAINT `pm_file_loves_file_id_files_id` FOREIGN KEY (`file_id`) REFERENCES `bak_rokgallery_files` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8

nicholas
Akeeba Staff
Manager
OK, you are using a very old version of Akeeba Backup which doesn't display the error message but you're lucky because I know what this particular case is (I've seen it before). When restoring please make sure that the "Suppress Foreign Key checks" is enabled. If you still have a problem, please delete all the pm_rokgallery_* tables from your database before trying the restoration.

After your site is restored please upgrade to Akeeba Backup 3.8.2 immediately! We have fixed some MAJOR issues between 3.7.6 and 3.8.2 (most of them actually fixed between 3.7.6 and 3.7.8). Your version is known to have some issues with the restoration script, especially with the (lack of) database error message reporting. This time you got lucky, I had seen the problem on this table again and I knew what it is. In any other case I wouldn't be able to help you.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user63935
Oh, Thank you - Thank you - Thank you!!!!

I am upgrading as I type this. Great help.

-

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!