Done
Details
Assignee
UnassignedUnassignedReporter
lpjirasynclpjirasync(Deactivated)Labels
Priority
Low
Details
Details
Assignee
Unassigned
UnassignedReporter
lpjirasync
lpjirasync(Deactivated)Labels
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created January 19, 2018 at 6:12 PM
Updated January 19, 2018 at 6:12 PM
Resolved January 19, 2018 at 6:12 PM
**Reported in Launchpad by Igor Tverdovskiy last update 23-05-2012 15:06:13
Hi,
innobackupex requires empty destination dir in order to copy backup to it. I think this is wrong behaviour, because target dir could/should contain custom my.cnf or master.info files. In such a case innobackupex should not consider non empty dir as error.
How to reproduce:
==
> ls -lh /var/192.168.1.7/mysql/
total 8,0K
rw-rw--- 1 mysql mysql 69 Feb 18 23:08 master.info
rw-r---- 1 mysql mysql 404 Feb 18 23:09 my.cnf
==
> sudo innobackupex --copy-back /var/tmps/backup
===
Original data directory is not empty! at /usr/bin/innobackupex line 574.
===
Fix:
I have modified template which decides whether directory is empty or not.
==
--if ( ! scalar( grep { $_ ne "." && $_ ne ".." } readdir($dh)) == 0) {
++if ( ! scalar( grep { $_ ne "." && $_ ne ".." && $_ ne "my.cnf" && $_ ne "master.info"} readdir($dh)) == 0) {
==