Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 22 Feb 2012 20:01:54 +0000 (UTC)
From: "Lars Hofhansl (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1640726298.5886.1329940914056.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1948061249.10800.1319038150893.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4618) HBase backups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213941#comment-13213941 ] 

Lars Hofhansl commented on HBASE-4618:
--------------------------------------

Are you planning to release the various tools you use as open source?
At Salesforce we need to get started seriously on backup procedures and I would like to avoid a lot of duplicate work.
                
> HBase backups
> -------------
>
>                 Key: HBASE-4618
>                 URL: https://issues.apache.org/jira/browse/HBASE-4618
>             Project: HBase
>          Issue Type: Umbrella
>          Components: documentation, regionserver
>            Reporter: Karthik Ranganathan
>            Assignee: Karthik Ranganathan
>
> We have been working on the ability to do backups in HBase with different levels of protection. This is an umbrella task for all the backup related changes. Here are some kinds of changes - will create separate issues for them:
> Roughly here are a few flavors of backups giving increasing levels of guarentees:
> 1. Per cf backups
> 2. Multi-cf backups with row atomicity preserved
> 3. Multi-cf backups with row atomicity and point in time recovery.
> On the perf dimension, here is a list of improvements:
> 1. Copy the files - regular hadoop "cp"
> 2. Use fast copy - copy blocks and stitch them together, saves top of rack bandwidth
> 3. Use fast copy with hard links - no file copy, it does only ext3 level linking.
> On the durability of data side:
> 1. Ability to backup data onto the same racks as those running HBase
> 2. Intra-datacenter backup
> 3. Inter datacenter backup
> Restores:
> 1. Restore with a table name different from the backed up table name
> 2. Restore a backed up table wen HBase cluster is not running at restore time
> 3. Restore into a live and running cluster
> Operationally:
> 1. How to setup backups in live cluster
> 2. Setting up intra-DC
> 3. cross-DC backups
> 4. Verifying a backup is good

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira