Your understanding is correct,
however one may ask, why it is needed to apply incremental backup twice ?
In regular workflow - you just apply incremental to full and may delete and
forget about it.
From that point of view this issue does not appear as high priority for me,
but it would be "nice to have"
On Fri, May 20, 2011 at 6:50 PM, Peter Zaitsev <email address hidden> wrote:
> Stewart,
>
> I think the bug description is consuming making it as non issue, While I
> think it is really serious design issue.
>
> The problem is the incremental backup itself is modified and can't be reused
> again for other restore. This requires
> extra copy operation which is not efficient.
>
> We do need to do the copy for non-incremental backup to put it back in place
> but it would be good we could essentially
> apply incremental backup from read only NFS volume, where they can be
> re-used to restore data to multiple slaves for example
>
> Vadim is my understanding correct ?
>
> On Fri, May 20, 2011 at 6:14 PM, Stewart Smith
> <email address hidden>wrote:
>
>> So this is just a feature request to be able to apply the incremental
>> backups to the same full backup repeatedly (essentially making it a no-
>> op as they're already applied)?.
>>
>> --
>> You received this bug notification because you are a member of Percona
>> developers, which is the registrant for Percona XtraBackup.
>> https://bugs.launchpad.net/bugs/782850
>>
>> Title:
>> incremental's xtrabackup_logfile is not reusable after applying log
>>
>> Status in Percona XtraBackup:
>> Triaged
>>
>> Bug description:
>> After we apply log from incremental changes - xtrabackup_logfile's
>> content changes and data from incremental dir cannot be used for
>> prepare again.
>>
>> It could be a nice feature if the contents is not changed - it will
>> allow to use incremental-dir for applying logs t full backup several
>> times.
>>
>
>
> --
> Peter Zaitsev, CEO, Percona Inc.
> Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
> 24/7 Emergency Line +1 888 401 3401 ext 911
>
> Percona Live MySQL Conference comes to NYC
> http://www.percona.com/live/nyc-2011/
>
> --
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona XtraBackup.
> https://bugs.launchpad.net/bugs/782850
>
> Title:
> incremental's xtrabackup_logfile is not reusable after applying log
>
> Status in Percona XtraBackup:
> Triaged
>
> Bug description:
> After we apply log from incremental changes - xtrabackup_logfile's
> content changes and data from incremental dir cannot be used for
> prepare again.
>
> It could be a nice feature if the contents is not changed - it will
> allow to use incremental-dir for applying logs t full backup several
> times.
>
Peter,
Your understanding is correct,
however one may ask, why it is needed to apply incremental backup twice ?
In regular workflow - you just apply incremental to full and may delete and
forget about it.
From that point of view this issue does not appear as high priority for me,
but it would be "nice to have"
On Fri, May 20, 2011 at 6:50 PM, Peter Zaitsev <email address hidden> wrote: /bugs.launchpad .net/bugs/ 782850 logfile' s www.percona. com/live/ nyc-2011/ /bugs.launchpad .net/bugs/ 782850 logfile' s
> Stewart,
>
> I think the bug description is consuming making it as non issue, While I
> think it is really serious design issue.
>
> The problem is the incremental backup itself is modified and can't be reused
> again for other restore. This requires
> extra copy operation which is not efficient.
>
> We do need to do the copy for non-incremental backup to put it back in place
> but it would be good we could essentially
> apply incremental backup from read only NFS volume, where they can be
> re-used to restore data to multiple slaves for example
>
> Vadim is my understanding correct ?
>
> On Fri, May 20, 2011 at 6:14 PM, Stewart Smith
> <email address hidden>wrote:
>
>> So this is just a feature request to be able to apply the incremental
>> backups to the same full backup repeatedly (essentially making it a no-
>> op as they're already applied)?.
>>
>> --
>> You received this bug notification because you are a member of Percona
>> developers, which is the registrant for Percona XtraBackup.
>> https:/
>>
>> Title:
>> incremental's xtrabackup_logfile is not reusable after applying log
>>
>> Status in Percona XtraBackup:
>> Triaged
>>
>> Bug description:
>> After we apply log from incremental changes - xtrabackup_
>> content changes and data from incremental dir cannot be used for
>> prepare again.
>>
>> It could be a nice feature if the contents is not changed - it will
>> allow to use incremental-dir for applying logs t full backup several
>> times.
>>
>
>
> --
> Peter Zaitsev, CEO, Percona Inc.
> Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
> 24/7 Emergency Line +1 888 401 3401 ext 911
>
> Percona Live MySQL Conference comes to NYC
> http://
>
> --
> You received this bug notification because you are a member of Percona
> developers, which is the registrant for Percona XtraBackup.
> https:/
>
> Title:
> incremental's xtrabackup_logfile is not reusable after applying log
>
> Status in Percona XtraBackup:
> Triaged
>
> Bug description:
> After we apply log from incremental changes - xtrabackup_
> content changes and data from incremental dir cannot be used for
> prepare again.
>
> It could be a nice feature if the contents is not changed - it will
> allow to use incremental-dir for applying logs t full backup several
> times.
>
-- tungle. me/VadimTkachen ko
Vadim Tkachenko, CTO, Percona Inc.
Phone +1-888-401-3403, Skype: vadimtk153
Schedule meeting: http://
Flat-rate 24x7 support for MySQL <http:// percona. com/mysql- support>