innobackupex: fatal error: no 'innodb_buffer_pool_filename'

MySQL & MariaDB Percona XtraBackup
1

Installed the 2.1.2 binary on linux and get the following error:

innobackupex: fatal error: no ‘innodb_buffer_pool_filename’ option in group ‘mysqld’ in MySQL options

At this point, only MyISAM tables are being backed up. Couldn’t find a way to not check this variable.

Searched the manual and the web and couldn’t find any help.

Any ideas?

Thanks,

Joe

2

Hi,

I’ve just tested the latest 2.1.2 with MySQL 5.6.11 and didn’t found that problem. I would need you to post your my.cnf and the MySQL version you are using so I can try to replicate the problem.

Thank you.

3

MySQL version 5.0.95

my.cnf

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql

Default to using old password format for compatibility with mysql 3.x

clients (those using the mysqlclient10 compatibility package).

#old_passwords=1

#set-variable=max_connections=256
set-variable=max_connections=512
log-slow-queries
long-query-time=1
log-bin=/var/lib/mysql/mysql-bin.log
max_binlog_size=25M
log-bin=mysql-bin

log everything on master, on replica filter using replicate-wild-do-table or replicate-wild-ignore-table = db.%

expire_logs_days=5
server-id=1
skip-bdb
skip-innodb

don’t set query cache higher than 200M

query-cache-size=64M
join_buffer_size=128K
tmp_table_size=256M
max_heap_table_size=256M
thread_cache_size=16
table_cache=512
key_buffer_size=256MB

[mysql.server]
user=mysql
basedir=/var/lib

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Thank you for checking, would really like to use this software to help with replication.

4

Ok, MySQL 5.0, that’s the problem. MySQL 5.0 it is not supported by xtrabackup so it fails. We only support (and test) MySQL 5.1 (InnoDB Plugin), 5.5 and 5.6 servers.

5

Hi @miguelangelniet i have faced the same problem in xtrabackup 2.1.3
Im using Mysql 5.5.27
innodb_buffer_pool_filename is introduced in 5.6.3

kindly help which version works perfectly with 5.5 version

6

i had the same issue, the problem was that there was two version of xtrabackup installed on backup source host. check that xtrabackup_55 and xtrabackup both is at 2.1.3