[
https://issues.apache.org/jira/browse/HBASE-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452786#comment-15452786
]
Vladimir Rodionov edited comment on HBASE-14417 at 8/31/16 5:12 PM:
--------------------------------------------------------------------
Delete file ref from hbase:backup after backup completes - do not keep them
there forever.
Now we have two different types of files in backup : HFile (snapshot/full), WAL
(incremental). Bulk load adds third type - HFile (bulk load/incremental)
* New storage layout for incremental backup image, that has bulk loaded files?
* Shipping HFiles to backup destination during incremental backup?
* The algorithm for restore incremental backup that has both : WALs and HFiles?
was (Author: vrodionov):
Delete file ref from hbase:backup after backup completes - do not keep them
there forever.
Now we have two different types of files in backup : HFile (snapshot/full), WAL
(incremental). Bulk load adds third type - HFile (bulk load/incremental)
*Shipping HFiles to backup destination
*New storage layout for incremental backup image, that has bulk loaded files?
*The algorithm for restore incremental backup that has both : WALs and HFiles?
> Incremental backup and bulk loading
> -----------------------------------
>
> Key: HBASE-14417
> URL: https://issues.apache.org/jira/browse/HBASE-14417
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Critical
> Labels: backup
> Fix For: 2.0.0
>
>
> Currently, incremental backup is based on WAL files. Bulk data loading
> bypasses WALs for obvious reasons, breaking incremental backups. The only way
> to continue backups after bulk loading is to create new full backup of a
> table. This may not be feasible for customers who do bulk loading regularly
> (say, every day).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
