Comment 5 for bug 717300

On 13 Feb 2011, at 11:01, Alexey Kopytov wrote:

> Is there really a change in the workflow after the fix for this bug?
> http://www.percona.com/docs/wiki/percona-
> xtrabackup:xtrabackup:incremental does not mention using innobackupex
> for incremental backups at all. So the only documented way is to use
> xtrabackup.

Alexey, FYI:

the innobackupex-1.5.1 documentation mentioned it was possible:
   --redo-only Options is used with --apply-log. This option forces to skip
               "rollback" phase and do only "redo". This is necessary to use
               if backup later will be applied with incremental changes.

And changelog of 1.4 mentioned that it was possible:
Incremental backups have changed and now allow the restoration of full backups containing certain rollback transactions that previously caused problems. Please see Preparing the Backupsand the --apply-log-only option. (From innobackupex, the --redo-only option should be used). (Yasufumi Kinoshita) (http://www.mysqlperformanceblog.com/2010/11/22/percona-xtrabackup-1-4/)

>
> What's different now is that:
>
> 1. innobackupex *may* be used now instead of xtrabackup to prepare the
> full backup.
>
> 2. innobackupex *may* be used now instead of xtrabackup to apply the
> incremental backup. This change is a result of the fixes for this bug
> and http://bazaar.launchpad.net/~percona-dev/percona-
> xtrabackup/trunk/revision/218
>
> So to me it looks more like an extension to the documented behavior
> rather than a change in the workflow.