You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2017/02/09 00:14:41 UTC

[jira] [Updated] (HBASE-17133) Backup documentation update

     [ https://issues.apache.org/jira/browse/HBASE-17133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Rodionov updated HBASE-17133:
--------------------------------------
    Fix Version/s: HBASE-7912

> Backup documentation update
> ---------------------------
>
>                 Key: HBASE-17133
>                 URL: https://issues.apache.org/jira/browse/HBASE-17133
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Vladimir Rodionov
>             Fix For: HBASE-7912
>
>
> We need to update backup doc to sync it with the current implementation and to add section for current limitations:
> {quote}
> - if you write to the table with Durability.SKIP_WALS your data will not
> be in the incremental-backup
>  - if you bulkload files that data will not be in the incremental backup
> (HBASE-14417)
>  - the incremental backup will not only contains the data of the table you
> specified but also the regions from other tables that are on the same set
> of RSs (HBASE-14141) ...maybe a note about security around this topic
>  - the incremental backup will not contains just the "latest row" between
> backup A and B, but it will also contains all the updates occurred in
> between. but the restore does not allow you to restore up to a certain
> point in time, the restore will always be up to the "latest backup point".
>  - you should limit the number of "incremental" up to N (or maybe SIZE), to
> avoid replay time becoming the bottleneck. (HBASE-14135)
> {quote} 
> Update command line tool section
> Clarify restore backup section
> Add section on backup delete algorithm
> Add section on how backup image dependency chain works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)