Support

Akeeba Backup for WordPress

#22026 During Restoration, WordPress Error: SQL=UPDATE...siteurl

Posted in ‘Akeeba Backup for WordPress’
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

WordPress version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Friday, 06 February 2015 07:43 CST

Thursday, 05 February 2015 10:39 CST

toad78
Greetings,

My issue isn't so much the backup but the restoration. During the restoration procedure, I have encountered this error on more than one occasion (see screenshot). I get to that point and then it's over. I can't continue.

I've used Akeeba on Joomla sites and never had any issues, but now working with WP seems to open a whole new can of worms.

Solution?

Thursday, 05 February 2015 11:26 CST

nicholas
I believe this was fixed in Akeeba Backup for WordPress 1.2.2.

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!

Thursday, 05 February 2015 14:29 CST

toad78
That's what I thought as well until I installed 1.2.2 and encountered the same thing.

Friday, 06 February 2015 02:33 CST

nicholas
As far as I can see in ticket 22013 you have not updated to 1.2.2. So, how exactly can you test something you can't install, let alone use?

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!

Friday, 06 February 2015 07:21 CST

toad78
After spending a few more hours trying to figure out why it wasn't working, I found out that it was the hosting server. How did I know? I was able to restore my backup with the use 1.2.2 on a different host without a problem.

Thank you for your patience.

Friday, 06 February 2015 07:43 CST

nicholas
That's interesting. You were trying to restore on GoDaddy, right? I assume that you might have bought one of their cheapest service levels. These come with several restrictions, one of them being the number of database command you can execute per minute. This limit is fine for very low traffic sites but it's a major problem when restoring backups. By definition, restoring a backup requires executing hundreds (if not thousands) of database commands to restore the entire database of the site. According to our experience you can usually work around that by asking your host to temporarily lift these limits while you're restoring your 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!

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!