Percona XtraBackup moved to https://jira.percona.com/projects/PXB

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

Bug #1164945 reported by Raghavendra D Prabhu on 2013-04-05

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Percona XtraBackup moved to https://jira.percona.com/projects/PXB	Fix Released	Wishlist	Alexey Kopytov	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.0
	2.0	Won't Fix	Undecided	Unassigned
	2.1	Fix Released	High	Alexey Kopytov	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1.6
	2.2	Fix Released	Wishlist	Alexey Kopytov	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.2.0

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:

Related branches

lp:~akopytov/percona-xtrabackup/bug1164945-2.1

Merged into lp:percona-xtrabackup/2.1 at revision 701

Alexey Kopytov (community): Approve on 2013-11-20

lp:~akopytov/percona-xtrabackup/bug1164945-2.2

Merged into lp:percona-xtrabackup/2.2 at revision 4903

Alexey Kopytov (community): Approve on 2013-11-20

Revision history for this message

Raghavendra D Prabhu (raghavendra-prabhu) wrote on 2013-04-05:

#1

Helps with lp:1098566

Raghavendra D Prabhu (raghavendra-prabhu) on 2013-06-24

tags:

added: pxc

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2013-09-04:

#2

See also bug #1193240.

Revision history for this message

Raghavendra D Prabhu (raghavendra-prabhu) wrote on 2013-09-16:

#3

Re. #2,

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

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2013-11-20:

#4

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

Revision history for this message

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-20:

#5

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-996

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.