Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7BAEA11F67 for ; Wed, 2 Apr 2014 11:24:19 +0000 (UTC) Received: (qmail 52160 invoked by uid 500); 2 Apr 2014 11:24:15 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 51617 invoked by uid 500); 2 Apr 2014 11:24:12 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 51606 invoked by uid 99); 2 Apr 2014 11:24:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 11:24:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aijwjia@gmail.com designates 74.125.82.193 as permitted sender) Received: from [74.125.82.193] (HELO mail-we0-f193.google.com) (74.125.82.193) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2014 11:24:05 +0000 Received: by mail-we0-f193.google.com with SMTP id w61so15728wes.0 for ; Wed, 02 Apr 2014 04:23:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=7pxtnmX0APO7BgxlOAVgLAxkgbMMUK6lnZY6kFgBjkI=; b=QJPXGu6LRsL0tj3XbCcueDGNPfbPVv0Td/L/uOrH/sHmp5wS9+y0KkY8f4CKFsSIF0 hFHwHXWn5EyJN7o6q131dqGSdD0ZTtRSElJfoPyk8+1kZF4L6xXzUqLn8IVJ//HfcgDR f73nrlHmfx8m3X7tQsT7BaFONzgDkajBhxxM1vDcoLe+BisBgrpVaT6eRvu5cs6i/T1X WvxXpDba/W76h26OYB8kHSNfDkG9nN7c0yGAk5yqNRHrhkJJkUhE6UnzD15464mavTP7 hQNgjFONrvU+RGuv4vWGQLrvqz6xvF9qgnAFwHH0GUETOS4jeP0eK5AZ/XMDDjA+38zE VYdQ== MIME-Version: 1.0 X-Received: by 10.180.21.225 with SMTP id y1mr1348267wie.24.1396437824709; Wed, 02 Apr 2014 04:23:44 -0700 (PDT) Received: by 10.216.1.196 with HTTP; Wed, 2 Apr 2014 04:23:44 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 Apr 2014 19:23:44 +0800 Message-ID: Subject: Re: What is the best practice for backup HBase data? From: R W To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7bb709887e2b4d04f60d84c9 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb709887e2b4d04f60d84c9 Content-Type: text/plain; charset=ISO-8859-1 Hi Esteban I checked the snapshot feature and tried myself, it's very good, one of the introduction http://blog.cloudera.com/blog/2013/03/introduction-to-apache-hbase-snapshots/mentioned about: Clone a snapshot: This operation creates a new table using the same schema > and with the same data present in the specified snapshot. The result of > this operation is a new fully functional table that can can be modified > with no impact on the original table or the snapshot. I think this clone operation will make a copy of the snapshot, then create the new table from the copy of the snapshot, am i correct? Otherwise, modification to the new table will change the snapshot, right? Another question, if we want to backup hbase data somewhere else, it seems we cannot go with snapshot feature, we want the data to be backup even after the whole Hadoop cluster down, any idea? Thanks aij On Wed, Apr 2, 2014 at 2:12 PM, Esteban Gutierrez wrote: > Hello Aij, > > Snapshots are the suggested method since HBase 0.94.6, they provide better > consistency for backing up data in HBase. You can find more information in > the HBase Book here: > > https://hbase.apache.org/book.html#ops.snapshots > > Depending on your use case and resources you might want to consider > replication as well: > > http://hbase.apache.org/replication.html > > cheers, > esteban. > > > -- > Cloudera, Inc. > > > > On Tue, Apr 1, 2014 at 10:56 PM, R W wrote: > > > Hi Guys > > > > I'm using hbase org.apache.hadoop.hbase.mapreduce.Export > > / org.apache.hadoop.hbase.mapreduce.Import to backup and restore HBase > > data, at least it's good to me, i would like to know if there are any > > better solutions or practices on how to backup HBase data, that will be > > really helpful for us, thanks. > > > > Cheers > > aij > > > --047d7bb709887e2b4d04f60d84c9--