That's true, I know of about a dozen. A couple more of mine, too. By now I understand the problem better: About half a year ago they moved a lot of web accounts to a new server. On the new server they changed the system of naming the databases, for example a db installed before the move was automatically named "usr_web999_1". If you backed it up on the server you can restore it again to an existent database "usr_web999_1", if its name is still intact. If by some mishap the database names get damaged, and not only their contents, there is the problem of the name. If you simply delete that damaged database and install a new one it will be named automatically "web999_db1". But the backup function cannot recognize it again, and your backup is fairly useless, unless you had downloaded it before your restoration attempt and get it now reconstructed manually. Once moved to the restoration folder it can't be downloaded anymore for direct insertion in phpMyAdmin apart from this database being already far too big for direct uploading via phpMyAdmin.
At the webhost they didn't understand that either. After I explained them they wrote me how sorry they are for the inconvenience caused by not having thought that over at the move.
We only lost a few posts and got everything running smoothly again. So no reason for complaining too much about the boys at the webhost. They're trying to do their best.
As to the other websites I lost, mai pen rai, that gives me opportunity to redo a few things I wasn't too happy with anyway. Life goes on!
