Hello,I've been using mylvmbackup (great tool, thanks!) in our production environment for backups. It has been working great without innodb recovery options, however when I tried turning on innodb recovery and it seems there is a snag. If you don't specify --socket=<something new> in the mysqld_safe parameter for mylvmbackup.conf, the spawned mysqld_safe process which is used for innodb recovery will use the socket from my.cnf which overwrites the old socket location. It is easy enough to specify the --socket option in the mysqld_safe parameter however I was hoping it might be possible to fix the behavior or at least document this behavior so other people using this tool don't find this the hard way :)
Just for note, I'm currently using 0.7 of mylvmbackup on Ubuntu 7.10. Thanks, Alain