Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-Id: <83CA1AC8-BB99-4C65-BD46-FBA21A5A99C6@wensel.net>
From: Chris K Wensel <chris@wensel.net>
To: hbase-user@hadoop.apache.org
In-Reply-To: <2f81e00902040821k328e1e81g2eaa48f99a425545@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Backup Again
Date: Wed, 4 Feb 2009 08:28:37 -0800
References: <2f81e00902040821k328e1e81g2eaa48f99a425545@mail.gmail.com>

Hey Michael

You could probably use Cascading to migrate data between HBase clusters.
http://wiki.apache.org/hadoop/Hbase/Cascading

But the code currently doesn't support multiple HBase cluster clients  
in a single JVM, but I'm sure it can be coded in quickly. (the code is  
hosted at github, so is easily cloned and patched).

A benefit of using Cascading would be the ability to put in quality  
checks, or filter data very easily.

I've already heard of users starting to migrate from HBase to a RDBMS  
using Cascading, and also between Hypertable and Aster Data. Hopefully  
those adapters will leak out for the rest of us to use.

ckw

On Feb 4, 2009, at 8:21 AM, Michael Dagaev wrote:

> Hi, all
>
>    I read HBASE-974 and HBASE-643 mentioned on the list
> but what do you think about copying tables from the production
> to a backup Hbase cluster ? I guess we do need a big iron
> for such a backup cluster.
>
> I understand that the copy can be implemented with MR
> but for now we can implement it just as a simple sequential script,
> which scans the tables of the production Hbase and writes the data
> to the backup Hbase.
>
> Does it make sense?
>
> Thank you for your cooperation,
> M.

--
Chris K Wensel
chris@wensel.net
http://www.cascading.org/
http://www.scaleunlimited.com/