innobackupex does not copy non-InnoDB files when applying incremental backups

[Valentine Gostev]

When prepraing an incremental backups, innobackupex should copy all non-InnoDB files (including .frm files and non-InnoDB tables) to the full backup directory. Otherwise, any changes to .frm and/or non-InnoDB tables made between full and incremental backups lead to unusable backups.

[Stewart Smith (stewart)]

Vadim, is this on your radar at all or shall I reassign?

[Vadim Tkachenko (vadim-tk)]

this is related
to
https://bugs.launchpad.net/percona-xtrabackup/+bug/783596
and
https://bugs.launchpad.net/percona-xtrabackup/+bug/771981

I will provide fix for all three bugs

[Vadim Tkachenko (vadim-tk)]

ok,

proper fix for this bug also requires copying MyISAM files back to full directory.
This logic is not implemented in innobackupex yet.

I un-assign bug from myself.

[Stewart Smith (stewart)]

Valentine, does this mean you're working on a real fix?

[Valentine Gostev (longbow)]

Stewart, yes, I have an idea about this. We have a copy-back function which places files back to mysql datadir - probably part of that code could be re-used for copying non-InnoDB files from inc to base basckup dir.

[Alexey Kopytov (akopytov)]

See also bug #903984.

[pservit (pservit)]

Shouldn't innobackupex delete files for tables dropped between incremental backups ?

[Alexey Kopytov (akopytov)]

On 24.02.12 0:43, pservit wrote:
> Shouldn't innobackupex delete files for tables dropped between
> incremental backups ?
>

Yes, that's https://bugs.launchpad.net/percona-xtrabackup/+bug/856400

Which is a lower priority, because leaving stale tables is probably a
lesser evil than not copying newly created ones.

[Shahriyar Rzayev (rzayev-sehriyar)]

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