Innobackupex or xtrabackup, problem : not running

Hello everynody,

I have a problem with xtrabackup on my mysql server.

When i running xtrabackup, This tool stops before to start the backup.

I run innobackup by :

innobackupex --no-lock --user=root --password=MyPassword /home/backup/full/

And i have in return :

[root@Myserver script_xtrabackup]# innobackupex --no-lock --user=root --password=MyPass /home/backup/full/InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oyand Percona Ireland Ltd 2009-2012. All Rights Reserved.This software is published underthe GNU GENERAL PUBLIC LICENSE Version 2, June 1991.130403 09:30:36 innobackupex: Starting mysql with options: --password=xxxxxxxx --user=‘root’ --unbuffered --130403 09:30:36 innobackupex: Connected to database with mysql child process (pid=20391)130403 09:30:42 innobackupex: Connection to database server closedIMPORTANT: Please check that the backup run completes successfully. At the end of a successful backup run innobackupex prints “completed OK!”.innobackupex: Using mysql Ver 14.14 Distrib 5.5.30, for Linux (x86_64) using EditLine wrapperinnobackupex: Using mysql server version Copyright © 2000, 2013, Oracle and/or its affiliates. All rights reserved.innobackupex: Created backup directory /home/backup/full/2013-04-03_09-30-42130403 09:30:42 innobackupex: Starting mysql with options: --password=xxxxxxxx --user=‘root’ --unbuffered --130403 09:30:42 innobackupex: Connected to database with mysql child process (pid=20457)130403 09:30:45 innobackupex: Connection to database server closed130403 09:30:45 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-group=“mysqld” --backup --suspend-at-end --target-dir=/home/backup/full/2013-04-03_09-30-42 --tmpdir=/home/tmp_mysqlinnobackupex: Waiting for ibbackup (pid=20472) to suspendinnobackupex: Suspend file '/home/backup/full/2013-04-03_09-30-42/xtrabackup_suspended’xtrabackup_55 version 2.0.6 for Percona Server 5.5.16 Linux (x86_64) (revision id: 521)xtrabackup: uses posix_fadvise().xtrabackup: cd to /home/mysqlxtrabackup: Target instance is assumed as followings.xtrabackup: innodb_data_home_dir = ./xtrabackup: innodb_data_file_path = ibdata1:10M:autoextendxtrabackup: innodb_log_group_home_dir = ./xtrabackup: innodb_log_files_in_group = 2xtrabackup: innodb_log_file_size = 268435456130403 9:30:45 InnoDB: Warning: allocated tablespace 237, old maximum was 9

xtrabackup stops for hours (7 or 8 hours) before of to begin the backup.

I think it is because of will flush all tables with READ LOCK.

But why with the –no-lock option, xtrabackup don’t move ?
why xtrabackup lasts as long as ?

Complementary information :

ibdata size : 7,3G

innodb option :


#innodb_data_file_path = ibdata1:10M:autoextend:max:2000M
innodb_data_file_path = ibdata1:10M:autoextend
innodb_buffer_pool_size= 30000M

Thank you


I guess, It’s not because of “Flush tables with read lock” as that read lock will be acquired at the end of the process when copying MyISAM tables and other files.

It can be due to initial process (aka, boot process) of xtrabackup which is similar to InnoDB boot process when MySQL server starts. What xtrabackup does in this process is, it opens and reads every .ibd files. You have enabled innodb_file_per_table so If you have lots of tables and slow I/O then might be booting step can take more time.

In this case, you can try with --parallel option to increase parallel threads for taking backup. nnobackupex_option_reference.html#cmdoption-innobackupex–pa rallel

Please check I/O subsystems and try to use --parallel=4 with xtrabackup if it helps.


Thanks for your response.

So, i running innobackupx with parallel option and indeed, it’s faster.

But we have decrease the number of .ibd files. may be that this has an effect.

Thanks again