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/07/08 17:43:00 UTC
[jira] [Updated] (HBASE-14135) HBase Backup/Restore Phase 3: Merge
backup images
[ https://issues.apache.org/jira/browse/HBASE-14135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Rodionov updated HBASE-14135:
--------------------------------------
Status: Patch Available (was: Open)
> HBase Backup/Restore Phase 3: Merge backup images
> -------------------------------------------------
>
> Key: HBASE-14135
> URL: https://issues.apache.org/jira/browse/HBASE-14135
> Project: HBase
> Issue Type: New Feature
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Blocker
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-14135-v3.patch
>
>
> User can merge incremental backup images into single incremental backup image.
> # Merge supports only incremental images
> # Merge supports only images for the same backup destinations
> Command:
> {code}
> hbase backup merge image1,image2,..imageK
> {code}
> Example:
> {code}
> hbase backup merge backup_143126764557,backup_143126764456
> {code}
> When operation is complete, only the most recent backup image will be kept (in above example - backup_143126764557) as a merged backup image, all other images will be deleted from both: file system and backup system tables, corresponding backup manifest for the merged backup image will be updated to remove dependencies from deleted images. Merged backup image will contains all the data from original image and from deleted images.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)