move-back/copy-back should allow non-empty directories in some cases

Bug #1164945 reported by Raghavendra D Prabhu on 2013-04-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to
Fix Released
Alexey Kopytov
Won't Fix
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description

It would be better if innobackupex has a --force to copy/move the
files. It helps in some cases as discussed over irc.

Tags: pxc Edit Tag help

Related branches

tags: added: pxc
Alexey Kopytov (akopytov) wrote :

See also bug #1193240.

Re. #2,

While issues in #1193240 have been addressed elswhere, the issue here will need to be fixed in innobackupex itself.

Alexey Kopytov (akopytov) wrote :

As I understand, the goal here is to implement an option to force --copy-back or --move-back to transfer files to directories, even if they are not empty. Overwriting existing _files_ in those directories should still be disallowed. That is, target directories for --copy-back/--move-back may contain other (temporary) subdirectories or files, which will never conflict with files being copied from the backup directory.

If that's correct, I'm going to implement the --force-non-empty-directories option. When specified, it will make --copy-back/--move-back skip the "empty directory" checks.

summary: - move-back/copy-back can do with force in some cases
+ move-back/copy-back should allow non-empty directories in some cases

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers