Here is how I see the issue
- innobackupex uses DBD::MySQL to talk to MySQL Server
- DBD::MySQL relies on libmysqlclient shipped with MySQL
- .mylogin.cnf support is built into libmysqlclient, this file is
always read
- in order to properly support .mylogin.cnf
- DBD::MySQL must be linked with correct version of libmysqlclient
- DBD::MySQL must provide an option to specify "--load-path"
- innobackupex must support "--load-path" option
- libmysqlclient must expose API to set "--load-path" value,
currently it only can be read from command line
I suggest first to check which version of libmysqlclient used by
DBD::MySQL on CentOS 6.
Here is how I see the issue
- innobackupex uses DBD::MySQL to talk to MySQL Server
- DBD::MySQL relies on libmysqlclient shipped with MySQL
- .mylogin.cnf support is built into libmysqlclient, this file is
always read
- in order to properly support .mylogin.cnf
- DBD::MySQL must be linked with correct version of libmysqlclient
- DBD::MySQL must provide an option to specify "--load-path"
- innobackupex must support "--load-path" option
- libmysqlclient must expose API to set "--load-path" value,
currently it only can be read from command line
I suggest first to check which version of libmysqlclient used by
DBD::MySQL on CentOS 6.