Thanks, I have been hearing the same thing from the MySQL team who is working to resolve that bug. I have to say I am a little surprised that the author(s) of MySQL Administrator did not anticipate that the database might be bigger than available physical memory ... I'd say that the surprise would be if the database was smaller!

I'll try the command-line approach but will mysqldump work fine while MySQL apps are running (in the sense that what it creates will be a consistent snapshot of my database) or do I need to stop all apps?

Regarding the restore procedure: the nice thing about MySQL Administrator is that it allows you to select which tables to restore. Using mysql on the backup file would not be selective - of course one is supposed to have primary keys on all tables so that it will not cause harm to (try to) restore the whole thing, but still, it is somehow disquieting to run thousands of statements attempting to re-insert rows with existing keys.