Comment 1 for bug 1241987

Revision history for this message
viljohakala (viljo-hakala) wrote : Re: Xtrabackup 2.1.5 (since 2.1.4) leaves unfinished backups around

In innobackupex code:

    open XTRABACKUP_PID, "> $option_tmpdir/$xtrabackup_pid_file";

Could this suggests that two simultaneous runs of innobackupex will write to same tmp/xtrabackup_pid_fie
when running ibbackup ?

Which could be avoided with: --tmpdir option ?

When I tested by running 2 copies of the backup script copies of different instances at the same time I didnt have issues.

Only when the logs are being scanned as suggested by this I have the problem:

xtrabackup: using O_DIRECT
>> log scanned up to (21810149)
[01] Copying /mariadb1/data/ibdata1 to /mariadb1/backup/2013-10-19_01-00-01/ibdata1
[01] ...done
>> log scanned up to (21810149)
xtrabackup: Creating suspend file '/mariadb1/backup/2013-10-19_01-00-01/xtrabackup_suspended_2' with pid '27051'
print() on closed filehandle XTRABACKUP_PID at /mariabin/percona-xtrabackup/bin/innobackupex line 2602.
131019 01:00:03 innobackupex: Waiting for ibbackup (pid=27051) to finish
-----