This gets archived though...
Yes. I was just about to look into this issue tomorrow, ie what is the
most convenient way to do what needs to be done on the remote hosts
that are being backed up. My first feeling is that your approach is a
good one. Might be especially advantageous as both XBM and xtrabackup
are developed heavily.
Note that you now have issues with 32 bit vs 64 bit binaries that XBM
must correctly autodetect which ones to use. Of course, we might as a
first step try just using the 32 bit binary everywhere - ask Percona
guys if it's safe and if there is a performance hit.
This seems like a good place to list some other issues that one needs
to guard against, all related to running xtrabackup on the remote
host, with correct permissions, etc...
* we should default to using "mysql" user on the remote host, so that
we have same permissions as mysqld.
* mysql user often has no password set, no shell and no home
directory in /etc/passwd. We should probably have an install shell
script that makes sure all of these are ok.
* The install script then also should take care of the ssh key setup.
* Finally, when I wanted to create a home directory for mysql, I
managed to do something where the directory existed but wasn't owned
nor writable by the mysql user. Resulted in obscure errors...
My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559