Support

Your host is blocking the restoration of the database from going on but they do not tell you why. According to our 11+ years of experience the most common causes -and their solutions- are:

1. Wrong database connection type. Try switching between MySQL (PDO), MySQL and MySQLi (note the trailing i!).
2. Your host has a web server security solution (e.g. mod_security2) with rules which get tripped when you use special characters in your database password. Try a database password consisting of only lowercase and uppercase English letters (a-z, A-Z) and numbers (0-9).
3. Your host enforces a maximum number of database commands (queries) over a set period of time, e.g. 1000 queries per minute. Since you are restoring your entire site's database we need to perform a large number of queries in a short amount of time. You can try setting the Maximum execution time to 1 and the Throttle time to 4000 (these settings are in the lower right corner in the database restoration page - the page in your screenshot) to make the restoration run 5 times slower.
4. Your host enforces a maximum number of requests over a set period of time (e.g. with mod_evasive). Again, the solution is the same as with the previous issue: you need to modify the maximum execution and throttle time to make the restoration run much slower.

It is possible that the limits set on the server are so low that even these solutions do not work. If you still can't restore the site you will need to contact the host and show them this reply of mine. Ask them to check their server logs to see why their server is halting the restoration and tell you. If it's a server limit ask them to temporarily raise or lift it so that you can restore the site. If they won't do that find a better host; unrealistically strict usage limits that the host won't lift even temporarily are typically the sign of a crowded server which leads to poor site performance and a negative impact in your search rankings and user engagement.