[
https://issues.apache.org/jira/browse/HBASE-29498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013409#comment-18013409
]
Vinayak Hegde edited comment on HBASE-29498 at 8/12/25 11:42 AM:
-----------------------------------------------------------------
Thanks, [~dieterdp_ng] — we’ll pick this up.
I have a couple of questions to understand this better:
{code:java}
Every backup root in use (i.e. for which at least one backup exists) causes
build-up of data that is not yet backed up (in that root). So this is an
important consideration for file usage. {code}
This refers to keeping the generated WAL files and bulk-loaded files from being
deleted from the source cluster until the incremental backup is completed, is
that correct?
{code:java}
Multi-root backups are already supported {code}
Could you share the Jira/commit that introduced this? I’d like to look into it
for my own understanding.
{code:java}
but should not be used yet until HBASE-28706 is fixed {code}
is this issue still unresolved? Is anyone planning to pick it up? Can we take
it on?
was (Author: JIRAUSER298877):
Thanks, [~dieterdp_ng] — we’ll pick this up.
I have a couple of questions to understand this better:
{code:java}
Every backup root in use (i.e. for which at least one backup exists) causes
build-up of data that is not yet backed up (in that root). So this is an
important consideration for file usage. {code}
This refers to keeping the generated WAL files and bulk-loaded files from being
deleted from the source cluster until the incremental backup is completed, is
that correct?
{code:java}
Multi-root backups are already supported {code}
Could you share the Jira/commit that introduced this? I’d like to look into it
for my own understanding.
{code:java}
but should not be used yet until HBASE-28706 is fixed {code}
is this issue still unresolved? Is anyone planning to pick it up? Can we take
it on?
> Explain backup roots
> --------------------
>
> Key: HBASE-29498
> URL: https://issues.apache.org/jira/browse/HBASE-29498
> Project: HBase
> Issue Type: Sub-task
> Reporter: Dieter De Paepe
> Priority: Major
>
> The concept of backup roots is not yet explained. I'm not sure whether that's
> the best user-facing name, but that's how it's called in the code. Things to
> mention that I can think of:
> * A backup root is the target destination of a backup, i.e. the backup_path
> in "{{{}hbase backup create <type> <backup_path>".{}}}
> * {{Every backup root in use (i.e. for which at least one backup exists)
> causes build-up of data that is not yet backed up (in that root). So this is
> an important consideration for file usage.}}
> * {{Conceptually, a backup root is a collection of full and incremental
> backups. It is independent of other backup roots. So it is not possible using
> HBase tooling to reuse the backup work done for one root for another root.}}
> * Multi-root backups are already supported, but should not be used yet until
> HBASE-28706 is fixed. However, section 3.3 (depending on interpretation) and
> section 14 (where it refers to HBASE-15476) mention this is not possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
