**Comment from Launchpad by: divyam goel on: 29-01-2014 01:38:41

Thanks,
This works

On Tue, Jan 28, 2014 at 1:22 AM, Sergei Glushchenko <
1273576@bugs.launchpad.net> wrote:

> hi!
>
> Looks like you used xtrabackup binary to prepare incremental backup.
> Please note that xtrabackup binary does not operate *.frm files and
> MyISAM tables. To *.frm files be copied properly you need to use
> innobackupex. See usage examples at http://www.percona.com/doc/percona-
> xtrabackup/2.1/innobackupex/incremental_backups_innobackupex.html.
>
> So far this bug report looks incorrect
>
> ** Changed in: percona-xtrabackup
> Status: New => Invalid
>
> –
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1273576
>
> Title:
> bug #759701 exists in 2.1.6, might have been brought back by some
> other chnage
>
> Status in Percona XtraBackup:
> Invalid
>
> Bug description:
> .frm files exist in incremental backup, but are not copied over to
> base dir in prepare step (sudo xtrabackup_55 --prepare --apply-log-
> only --target-dir=base_dir_path --incremental-dir=incr_dir_path)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1273576/+subscriptions
>

**Comment from Launchpad by: Sergei Glushchenko on: 28-01-2014 09:22:17

hi!

Looks like you used xtrabackup binary to prepare incremental backup. Please note that xtrabackup binary does not operate *.frm files and MyISAM tables. To *.frm files be copied properly you need to use innobackupex. See usage examples at http://www.percona.com/doc/percona-xtrabackup/2.1/innobackupex/incremental_backups_innobackupex.html.

So far this bug report looks incorrect