[
https://issues.apache.org/jira/browse/HBASE-28084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844462#comment-17844462
]
Ray Mattingly commented on HBASE-28084:
---------------------------------------
{quote}Imagine I have a set of backups (Full1, Incr2, Incr3), delete the last
backup (Incr3), and then create a new incremental backup (Incr4).
This backup history will now show: Full1, Incr2, Incr4.
{quote}
In this case shouldn't Incr4 recognize that the last existing backup is Incr2,
so Incr4 would cover from the end of Incr2 to now if possible (WALs are still
around?) or throw if this is not possible?
I'm concerned that this proposal would mean that any incremental backup
corruption or ungraceful failures would necessitate a new full backup. A nicer
UX would be to delete the bad incremental backup, and try again
> Incremental backups should be forbidden after deleting backups
> --------------------------------------------------------------
>
> Key: HBASE-28084
> URL: https://issues.apache.org/jira/browse/HBASE-28084
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
> Reporter: Dieter De Paepe
> Priority: Major
>
> Imagine I have a set of backups (Full1, Incr2, Incr3), delete the last backup
> (Incr3), and then create a new incremental backup (Incr4).
> This backup history will now show: Full1, Incr2, Incr4.
> However, restoring Incr4 will not contain the data that was captured in
> Incr3, effectively leading to data loss. This will certainly surprise some
> users.
> I suggest to add some internal bookkeeping to prevent incremental backups in
> case the most recent backup was deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
