Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

LP #1164945: move-back/copy-back should allow non-empty directories in some cases

Description

**Reported in Launchpad by Raghavendra D Prabhu last update 20-11-2013 09:28:10

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

Environment

None

Smart Checklist

Activity

lpjirasync January 19, 2018 at 7:41 PM

**Comment from Launchpad by: Alexey Kopytov on: 20-11-2013 06:26:18

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.

lpjirasync January 19, 2018 at 7:41 PM

**Comment from Launchpad by: Raghavendra D Prabhu on: 16-09-2013 20:21:16

Re. #2,

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

lpjirasync January 19, 2018 at 7:41 PM

**Comment from Launchpad by: Alexey Kopytov on: 04-09-2013 11:26:13

See also bug #1193240.

lpjirasync January 19, 2018 at 7:41 PM

**Comment from Launchpad by: Raghavendra D Prabhu on: 05-04-2013 11:02:12

Helps with lp:1098566

Done

Details

Assignee

Reporter

Labels

Priority

Smart Checklist

Created January 19, 2018 at 7:40 PM
Updated January 19, 2018 at 7:41 PM
Resolved January 19, 2018 at 7:41 PM