[
https://issues.apache.org/jira/browse/HBASE-29261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayak Hegde resolved HBASE-29261.
-----------------------------------
Resolution: Fixed
> Investigate flaw in backup deletion validation of PITR-critical backups and
> propose correct approach
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-29261
> URL: https://issues.apache.org/jira/browse/HBASE-29261
> Project: HBase
> Issue Type: Task
> Components: backup&restore
> Reporter: Vinayak Hegde
> Assignee: Vinayak Hegde
> Priority: Major
> Labels: pull-request-available
>
> This Jira investigates a flaw in our current logic used to validate whether a
> full backup—potentially critical for PITR (Point-In-Time Recovery)—can be
> safely deleted.
> The current approach incorrectly checks whether a full backup is the only
> valid base for *all* PITR target points, which is not a valid criterion. A
> full backup should not be required to support _all_ PITR points to be
> considered necessary. Instead, each full backup only contributes to a
> {*}specific PITR time range{*}, depending on when the backup was taken and
> the availability of continuous backups afterward.
> This ticket proposes a more accurate and conservative approach:
> * Determine the PITR range each full backup can support.
> * Identify if another full backup exists that fully covers the same range.
> * If such a backup exists, the original one can be considered safe for
> deletion.
> All edge cases and reasoning are explained in the comments for clarity.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
