Hi doug,
On Thu, 23 May 2013 15:16:47 -0700 (PDT), doug wrote:
> 130523 21:56:14 innobackupex: Connecting to MySQL server with DSN
> 'dbi:mysql:;mysql_read_default_file=/etc/my.cnf;mysql_read_default_group=xtrabackup;mysql_socket=/var/run/mysqld/mysqld.sock'
> as 'xrepl' (using password: YES).
> ^GCharacter set 'utf8mb4' is not a compiled character set and is not
> specified in the '/usr/share/mysql/charsets/Index.xml' file
> ERROR: Failed to connect to MySQL server: DBI
> connect(';mysql_read_default_file=/etc/my.cnf;mysql_read_default_group=xtrabackup;mysql_socket=/var/run/mysqld/mysqld.sock','xrepl',...)
> failed: Can't initialize character set utf8mb4 (path:
> /usr/share/mysql/charsets/) at /usr/bin/innobackupex line 1384
>
> Is this a known bug?
>
It appears to be a DBD::mysql issue in old Ubuntu distributions. In
Ubuntu 10.04 DBD::mysql is linked against libmysqlclient16, i.e. the 5.1
client library. However, utf8mb4 is only supported in 5.5, which means
any DBD::MySQL utility on Ubuntu 10.04 is unable to connect to 5.5
servers if utf8mb4 is used as the default character set.
The workaround is to add "default-character-set=latin1" to either
[client] or [xtrabackup] group in my.cnf.
/Alexey