Automated message: This issue was created using the Report Issue Wizard on the Composr homesite.

The backups addon was always intended to be a last resort for people who couldn't get a proper backup system for whatever reason. I don't think we should be investing in it as a priority. Any decent hosting control panel should have a backup system, and there are many options at the server-level. It's much more a feature of a control panel than a CMS, and if we are seeing that the features inside control panels are insufficient - the fact that the large corporations behind those can't do a good job, suggests we shouldn't be trying to do so either. Unless someone throws 100k our way and asks us to.
That's my view.

I see an advantage to the Composr CMS backup system in some cases though: the fact the restoration process does not use whole database dumps directly and instead processes a PHP script bit by bit. This has helped me in some cases where the upload limit wasn't high enough on a server to import a dump (and the webhost locks down the backups so I can't extract them / import them via SSH either).

I do agree though when possible, server backups are the way to go.

This was particularly a client request, so I'm going to change the status to sponsorship. If they want it, I'll have them contract me for the feature.

Ok. FYI BigDump is really nice https://www.ozerov.de/bigdump/

I tried that, but it doesn't work on my environment. I think it might have to do with PHP 8. I eventually found the HeidiSQL client to work for large imports. It does imports in chunks as well, and since it connects directly to the db server, no web server is involved. Of course it requires that the db server can be accessed outside of the server itself.