Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <264230368.1259092179732.JavaMail.jira@brutus>
Date: Tue, 24 Nov 2009 19:49:39 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2008) [EC2] Periodic automatic backup to
 S3
In-Reply-To: <2083101422.1259091939724.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-2008:
---------------------------------------

Consider an easy way for the user to back up an elastic HBase cluster to S3. 

distcp is too naive an approach. Compactions rewrite data into new files. 

One option is a tool, probably MapReduce in formulation, that incrementally writes new edits (stores and delete markers) into log structured files in S3, and conversely can reply from S3 back into HBase. 

Another option is to hook replication (HBASE-1295) at least for the backup piece. 

> [EC2] Periodic automatic backup to S3
> -------------------------------------
>
>                 Key: HBASE-2008
>                 URL: https://issues.apache.org/jira/browse/HBASE-2008
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.