Support

There's a reason why this feature was removed. This backup type has a single, large database dump file. On some servers it causes a lot of trouble trying to restore it. That's why all other backup types which take a database dump do so in smaller chunk files. The only use case for the “Database Only (SQL File)” backup type is when you have a legitimate reason to want to use the command line mysql command, or your host-provided phpMyAdmin / Adminer installation to restore the database. In both cases, there is no time limit, and an ample memory limit to prevent all the issues importing a single, large database dump file would entail. This is something that has to do with how the host configures the server, not something in the programming of either software (from a programming point of view, they are much simpler than the database restoration code in our restoration script). Our limiting factor is the artificial limitations imposed by hosting companies on how we can use their servers.

If you want to allow users to import a database themselves, change the backup type to “All Configured Databases”. This creates a backup archive file, it splits the database dump in small chunks (making it possible to import the database backup efficiently), and includes the restoration script — it's like a Full Site Backup, but without backing up the site's files. That backup type can be used with the Restore feature already present in the backend.