Support

Site Restoration

#12422 Can't restore site

Posted in ‘Site restoration’
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

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Friday, 25 May 2012 10:44 CDT

user63964
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: (unknown)
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version which took the backup: (unknown)
Kickstart version used to extract the backup: (unknown)

Description of my issue:

I have tried to restore a site to a different server but am getting the following error:

Error at the line 61: REPLACE INTO `#__comprofiler` VALUES ('469', '469', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '0', '0000-00-00 00:00:00', '81.159.0.14', 'reg8d2fdc8d8a7dedb7f3e04f88c392b1e30c ... MySQL: MySQL query failed with error 1064 (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1). The query was:REPLACE INTO `jos_comprofiler` VALUES ('469', '469', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '0', '0000-00-00 00:00:00', '81.159.0.14', 'reg8d2fdc8d8a7dedb7f3e04f88c392b1e30c32f291', '0', NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL), ('470', '470', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '1', '0000-00-00 00:00:00', '2.99.82.148', '', '0', NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL), ('471', '471', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '1', '0000-00-00 00:00:00', '92.233.46.225', '', '0', NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL), ('472', '472', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '1', '0000-00-00 00:00:00', '78.147.13.190', '', '0', NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL), ('473', '473', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '1', '0000-00-00 00:00:00', '88.109.74.98', '', '0', NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL), ('474', '474', NULL, NULL, NULL, '0', '0000-00-00 00:00:00', '0', NULL, '1', '1', '1', '0000-00-00 00:00:00', '83.244.130.66', '', '0', NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL), ('475', '475', NULL, NU

nicholas
Akeeba Staff
Manager
I need the following information for the site you take the backup from:

Joomla! version:
PHP version:
MySQL version:
Akeeba Backup version which took the backup:

And the following information for the site you are restoring to:
PHP version:
MySQL version:
Kickstart version used to extract the backup:
Is the database collation set to UTF-8?

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!

user63964
I need the following information for the site you take the backup from:
Joomla! version: 2.5.4
PHP version:3.4.10.1
MySQL version:5.0.91-community-cll
Akeeba Backup version which took the backup:Akeeba Backup Professional 3.5.0

And the following information for the site you are restoring to:
PHP version:3.4.10.1
MySQL version:5.1.62-cll
Kickstart version used to extract the backup: used site transfer wizard
Is the database collation set to UTF-8? yes

nicholas
Akeeba Staff
Manager
There is no way you have PHP 3.4. This sounds like a phpMyAdmin version. Is your PHP version 5.2, 5.3 or 5.4?

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!

user63964
my bad, you are right.

Coming fron server with 5.2.17

going to server with 5.3.10

nicholas
Akeeba Staff
Manager
OK, these are both supported environments. It seems that the MySQL maximum packet size, though, is set a little lower. Back to the original site go to Akeeba Backup's configuration page and click the "Configure..." button next to the Database Dump Engine. Select a maximum packet size of 64Kb and retake a backup. Now try restoring this backup on the new server. It should restore the database properly this time.

If that works, please tell me which is the target host. I've started observing a pattern for a particular host and I'd like to make sure that it's a hosting limitation so that I can change the default packet size in Akeeba Backup and the troubleshooting instructions.

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!

user63964
THanks Nicholas, I will try that.

Just to be sure though, you mean the setting highlighted in this screencast:

http://screencast.com/t/dSAaV6HB

nicholas
Akeeba Staff
Manager
Yes, exactly!

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!

user63964
OK, I have tried to redo the STW but received the following error:

[120525 10:39:47] Uploading administrator/components/com_joomailermailchimpintegration/controllers/create.php has failed.

[120525 10:39:47] ----- Finished operation 1 ------

[120525 10:39:47] Failed Smart algorithm on AECoreDomainPack


I checked the cpanel of destination server and disk usage is full (even though backup is 350Mb and disk space is 500Mb. I guess this is the cause?

nicholas
Akeeba Staff
Manager
Yes, that's the reason. Coincidence: I was actually having the same problem with a site of mine I was transferring between hosting account just a few minutes ago :) The solution is rather simple:
- Take a backup
- Download the backup to your PC
- Use Akeeba eXtract Wizard to extract it
- Upload all files except the .htaccess and php.ini files (if the exist) to the new host. This takes a while.
- Go to http://www.example.com/installation/index.php where www.example.com is your new site's domain name
- Follow the restoration procedure
- Remove the installation directory
- If you had .htaccess and php.ini files copy them to the new site

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!

user63964
HI Nicholas, thanks for the advice but I needed to increase the server space anyway, and as ftp takes so long from my location I thought this would be easier.

I upgraded my account and started the process again and it all worked perfectly - thank you for your prompt help and feedback.

nicholas
Akeeba Staff
Manager
Excellent! I am glad it's all working now :)

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!

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!