You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Demai Ni (JIRA)" <ji...@apache.org> on 2014/04/27 01:16:15 UTC
[jira] [Assigned] (HBASE-11085) Incremental Backup Restore support
[ https://issues.apache.org/jira/browse/HBASE-11085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Demai Ni reassigned HBASE-11085:
--------------------------------
Assignee: Demai Ni
> Incremental Backup Restore support
> ----------------------------------
>
> Key: HBASE-11085
> URL: https://issues.apache.org/jira/browse/HBASE-11085
> Project: HBase
> Issue Type: New Feature
> Reporter: Demai Ni
> Assignee: Demai Ni
> Fix For: 1.0.0
>
>
> the jira is part of [HBASE-7912|https://issues.apache.org/jira/browse/HBASE-7912], and depend on full backup [HBASE-10900| https://issues.apache.org/jira/browse/HBASE-10900 ].
> When client issues an incremental backup request, BackupManager will check the request and then kicks of a global procedure via HBaseAdmin for all the active regionServer to roll log. Each Region server will record their log number into zookeeper. Then we determine which log need to be included in this incremental backup, and use DistCp to copy them to target location
> Restore is to replay the backuped WAL logs on target HBase instance. The replay will occur after full backup.
> As incremental backup image depends on prior full backup image and incremental images if exists. Manifest file will be used to store the dependency lineage during backup, and used during restore time for PIT restore.
--
This message was sent by Atlassian JIRA
(v6.2#6252)