Support

Site Restoration

#13022 Database Dump hangs at 50%

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 Tuesday, 24 July 2012 04:46 CDT

Tuesday, 24 July 2012 04:06 CDT

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

Description of my issue:
This is probably not an issue with akeeba. One of the restoration on my client's homebrew server hangs at 50% when restoring the database. It can communicate with the database but the dump hangs. I can restore the package on another server. Any idea what will cause this?

Regards

Tuesday, 24 July 2012 04:28 CDT

nicholas
First, let me correct you. It's the restoration, not the dump, which hangs. Dump is when you take the data from a database to a file. Restoration is when you take the data from a file to a database. Since you're talking about site restoration, it's database restoration.

I can think of a few reasons why it hangs:
- The PHP timeout is set very low, causing the restoration to hang
- The MySQL packet limit is set very low. However you'd get an error, not just a hang
- There is a query limit per hour set up on the MySQL server. That's a little crazy to do on a homebrew server and it should result to an error.
- The connection between the browser and the server is flakey, causing the process to hang indefinitely waiting for an acknowledgment from the server which never comes.
- The server has a very slow disk (e.g. consumer-grade SATA). After you restore a bunch of data to the MySQL server it will try to dump its data cache to disk. On slow disks this may take a substantial amount of time, triggering a timeout error or causing the server to return no data. If PHP is running as CGI or FastCGI the latter issue is very common when the execution takes too long.

The only workaround is using the manual method described in our documentation as the last resort for restoring your backups.

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!

Tuesday, 24 July 2012 04:38 CDT

user27992
Thanks for your great reply! it was a big help.

Regards

Tuesday, 24 July 2012 04:46 CDT

nicholas
You're welcome!

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!