# xtrabackup prepare problem

**URL:** <https://forums.percona.com/t/xtrabackup-prepare-problem/2189>\
**Category:** Percona XtraBackup\
**Created:** [December 5, 2011, 6:48pm UTC](https://forums.percona.com/t/xtrabackup-prepare-problem/2189 "2011-12-05T18:48:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kinnaur](https://avatars.discourse-cdn.com/v4/letter/k/f04885/32.png) [@kinnaur](https://forums.percona.com/u/kinnaur)\
**Post date:** [December 5, 2011, 6:48pm UTC](https://forums.percona.com/t/xtrabackup-prepare-problem/2189/1 "2011-12-05T18:48:12Z")

</div>

Hello,

I’m running Debian 6.0.2,  
mysqld Ver 5.5.17-55-log for Linux on x86\_64 (Percona Server (GPL), Release 22.1)

I’m creating backup doing:  
xtrabackup\_55 --backup --datadir=/var/lib/mysql --target-dir=/home/la/backup/

the create phase runs few minutes (the dataset is about 5G), and exits cleanly.

but prepare phase quickly fails:  
$xtrabackup\_55 --prepare --target-dir=/home/la/backup/

xtrabackup\_55 version 1.6.3 for Percona Server 5.5.9 Linux (x86\_64) (revision id: undefined)  
xtrabackup: cd to /home/la/backup/  
xtrabackup: This target seems to be not prepared yet.  
xtrabackup: No valid checkpoint found.  
xtrabackup: Error: xtrabackup\_init\_temp\_log() failed.

I’m doing exactly the same steps as documentation says.

Here is some last lines of strace output:

open(“./xtrabackup\_logfile”, O\_RDWR) = 3  
fadvise64(3, 0, 0, POSIX\_FADV\_SEQUENTIAL) = 0  
fadvise64(3, 0, 0, POSIX\_FADV\_DONTNEED) = 0  
lseek(3, 0, SEEK\_END) = 17416192  
mmap(NULL, 2117632, PROT\_READ|PROT\_WRITE, MAP\_PRIVATE|MAP\_ANONYMOUS, -1, 0) = 0x7f09aa5e7000  
pread(3, "\0\0\0\0\0\0\0\1?\376\200\0\0\0\0\0xtrabkup 111206 "…, 2048, 0) = 2048  
write(2, "xtrabackup: No valid checkpoint "…, 39xtrabackup: No valid checkpoint found.  
) = 39  
close(3) = 0  
munmap(0x7f09aa5e7000, 2117632) = 0  
write(2, “xtrabackup: Error: xtrabackup\_in”…, 54xtrabackup: Error: xtrabackup\_init\_temp\_log() failed.  
) = 54  
exit\_group(1) = ?

---

<div class="post-metadata">

**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\
**Post date:** [December 6, 2011, 3:27pm UTC](https://forums.percona.com/t/xtrabackup-prepare-problem/2189/2 "2011-12-06T15:27:57Z")

</div>

Looks like a bug at first glance.

---

<div class="post-metadata">

**Author:** ![kinnaur](https://avatars.discourse-cdn.com/v4/letter/k/f04885/32.png) [@kinnaur](https://forums.percona.com/u/kinnaur)\
**Post date:** [December 6, 2011, 4:50pm UTC](https://forums.percona.com/t/xtrabackup-prepare-problem/2189/3 "2011-12-06T16:50:02Z")

</div>

Maybe I can gather some additional information about this bug? Can you advice where to look?

here is my.cnf:

user = mysql  
pid-file = /var/run/mysqld/mysqld.pid  
socket = /var/run/mysqld/mysqld.sock  
port = 3306  
basedir = /usr  
datadir = /var/lib/mysql  
tmpdir = /tmp  
language = /usr/share/mysql/english

skip-external-locking  
bind-address = 127.0.0.1  
myisam-recover = BACKUP  
expire\_logs\_days = 10  
max\_binlog\_size = 100M  
back\_log = 75

log\_slow\_queries=/var/log/mysql/slow\_queries.log  
long\_query\_time=0.2  
log\_error = /var/log/mysql/mysql-error.log

max\_connections = 300  
key\_buffer = 16M  
myisam\_sort\_buffer\_size=16M  
join\_buffer\_size = 8M

table\_cache = 132656  
thread\_cache\_size = 384  
wait\_timeout = 60  
connect\_timeout = 3  
tmp\_table\_size = 128M  
max\_heap\_table\_size = 128M  
max\_allowed\_packet = 64M  
max\_connect\_errors = 10

query\_cache\_size = 128M  
query\_cache\_type = 1  
query\_cache\_min\_res\_unit=512  
max\_connect\_errors = 10000  
query\_prealloc\_size = 163840  
query\_alloc\_block\_size = 32768

default-storage-engine = innodb

innodb\_log\_files\_in\_group=2  
innodb\_log\_file\_size=512M  
innodb\_buffer\_pool\_size = 6000M  
innodb\_thread\_concurrency=8  
innodb\_flush\_method = O\_DIRECT  
innodb\_file\_per\_table = 1  
innodb\_flush\_log\_at\_trx\_commit = 2  
innodb\_additional\_mem\_pool\_size = 20M  
transaction-isolation=READ-COMMITTED  
innodb\_adaptive\_flushing\_method=keep\_average  
innodb\_flush\_neighbor\_pages=1  
innodb\_log\_block\_size=4096