Support

Your database backup is 4132100 bytes, or 3.94 Mb. That's a tiny database. Our database backup is a little over 1Gb, more than 250 times more than yours and it's restoring just fine.

The problem I suspect is your host having a MySQL query limit. This means that they allow you to execute a specific number of database operations in a limited amount of time, e.g. 100 queries (database operations) per second. Since the database restoration needs to do a LOT of database operations in a limited amount of time the limit kicks in and halts the restoration script. Please contact your host.

I believe that the problem with the progress bar has to do with the very big size of your database dump, after all. Most PHP versions (anything except the 64-bit PHP on 64-bit Linux) can only handle integers up to 2147483647 which is 2Gb minus one byte. A database backup that's nearly 4Gb will cause miscalculations in the total size and percentage determination. There is a solution to that, but it requires the BCMath extension for PHP which is seldom (if ever) installed on hosts and local server environments. As a result using that solution would break the restoration script for everyone – so it's not a viable solution. You'll have to leave with the lack of feedback I'm afraid.

Which brings me to the next point. How did you end up with a 4Gb database dump?! It would appear that you are backing up analytics data which would ideally be excluded from the backup, or that you are storing entire files in your database which is a really bad practice.

You're welcome! And thank you for explaining how you got that huge database dump. It's good to know just how big of a database dump our software can handle on real world servers, live and local.