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 980267077 for ; Thu, 14 Jul 2011 17:00:26 +0000 (UTC) Received: (qmail 35856 invoked by uid 500); 14 Jul 2011 17:00:24 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 35776 invoked by uid 500); 14 Jul 2011 17:00:24 -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 35768 invoked by uid 99); 14 Jul 2011 17:00:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jul 2011 17:00:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.169] (HELO mail-vx0-f169.google.com) (209.85.220.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Jul 2011 17:00:15 +0000 Received: by vxg38 with SMTP id 38so490665vxg.14 for ; Thu, 14 Jul 2011 09:59:54 -0700 (PDT) Received: by 10.52.22.144 with SMTP id d16mr2816686vdf.513.1310662794145; Thu, 14 Jul 2011 09:59:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.115.129 with HTTP; Thu, 14 Jul 2011 09:59:34 -0700 (PDT) X-Originating-IP: [64.105.168.204] In-Reply-To: References: <84B5E4309B3B9F4ABFF7664C3CD7698302D0DC92@kairo.scch.at> From: Ted Dunning Date: Thu, 14 Jul 2011 09:59:34 -0700 Message-ID: Subject: Re: HBase backup and outage scenarios in practice? To: user@hbase.apache.org, Michael Segel Content-Type: multipart/alternative; boundary=20cf307d05c243ed6604a80a760f X-Virus-Checked: Checked by ClamAV on apache.org --20cf307d05c243ed6604a80a760f Content-Type: text/plain; charset=ISO-8859-1 To clarify what Mike means here, MapR supports HBase as well as atomic, transactionally correct snapshots. These snapshots allow point in time recovery of the complete state of an HBase data set. There is no performance hit when taking the snapshot and no maintenance impact relative to HBase administration. Snapshots can be scheduled or invoked manually. We also provide transactionally correct mirrors that have similar characteristics but which allow actual copies to be made, possibly between clusters. This isn't quite related to HBase itself since MapR simply provides a substrate on which to run HBase (and distributes the Apache released bits for convenience). On Thu, Jul 14, 2011 at 9:14 AM, Michael Segel wrote: > Not sure what you read in Otis' bog but pretty ssure it's out of date. > > Check out MapR stuff. > > > > Sent from my Palm Pre on AT&T > On Jul 14, 2011 6:57 AM, Steinmaurer Thomas > wrote: > > Hello, > > > > > > > > we are currently evaluating HBase for a project. In respect to available > > backup options, we found the following blog post here: > > > > http://blog.sematext.com/2011/03/11/hbase-backup-options/ > > > > > > > > Probably well known for you guys here. So, am I right when I say that > > there is no online (consistent backup while the system is in use) and > > incremental backup utility we are used from the RDBMS world? > > > > > > > > We would also like to try out various outage scenarios, e.g. pulling the > > network cable out of one node or resetting the server etc ... while the > > system is in use ... Anybody tried different outage scenarios with > > HBase? > > > > > > > > Thanks! > > > > > > > > Thomas > > > > > > > > > > > --20cf307d05c243ed6604a80a760f--