Thanks for your readiness to help. Alas, the dump I created the other day is of course out-dated, so it's no real use anymore. What I'll do instead is writing a backup tool as suggested in [help wanted]:MySQL backup system. Once it's done, I'll use it to move over. The idea is that the tool will create a dump file on the server, with only a few lines of queries done at a time (which get appended to the dump file on the server's file system), with a refresh of the page done every xx seconds that will do another few steps. This way, a dump file will be built gradually that will not run into timeouts, no matter what. The same process will be used to restore the dump: little by little (several hundred queries only). It will have only small impact on the mysql server when run, only some http traffic impact and a large local dumpfile. I will publish the script once it's finished as well.
Well that sounds like a plan... Ironically since you tried the move, the server has been much more responsive that it was before... I have no idea why that would be.
So I guess you don't have a mysql admin page that will do the dump?
BTW, you still have the announcement for the old upgrade plan coming up in the news box occassionally...
In other news, I got some SSI stuff working for cpmfetch - I am debating what to do with that part of it - so I am going to defer it for a little while and wrap up some other odds and ends. I think all the major functionality is spoken for at this point, just a few funky requests from people.
I also renamed the main files to cpmfetch.php instead of coppermine.php - figured it would be cleaner this way.
Good luck, lemme know if you need anything