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 9F1CD11560 for ; Sat, 6 Sep 2014 21:34:08 +0000 (UTC) Received: (qmail 15886 invoked by uid 500); 6 Sep 2014 21:34:06 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 15809 invoked by uid 500); 6 Sep 2014 21:34:06 -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 15797 invoked by uid 99); 6 Sep 2014 21:34:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Sep 2014 21:34:06 +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 svarma.ng@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Sep 2014 21:34:02 +0000 Received: by mail-la0-f46.google.com with SMTP id pv20so15622249lab.19 for ; Sat, 06 Sep 2014 14:33:40 -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=vQGh/haZ9Bnhms/49Tvehl/BzPBfaPNTuVYpsyvCkKg=; b=PklHq1eYfRkhjHlyNSxXbooR+wTVa1Et9RLgfAEAbZ8R96/mbmO5GH8Wcy8yFEMCi1 ESZaRNdxUviYNyJi/pHIvKF9ghF1MQKNCbxrgLm8gNV9oEIWnxJ9ZusCCpyjtBViD7L2 WtQCYam98t/x65uCoDaP1Pua2JePzQalrzNUgH7oKtVGT+0WqZRt+jS0U530mqTuE7Uj pDyXPsV/TCgwGZpm+M7UlnJn5s4NBz0ODls3pzwh3WiUFK/pnZU4B6gW5N1G4PB3e+mj 6z4KLHZ3Ecrd/o1sStlTo20upD8ZS1pAJochgiNQlwQqi5RVq7L1105x5HVO9+Xm+JTF FpKw== MIME-Version: 1.0 X-Received: by 10.152.203.167 with SMTP id kr7mr4455535lac.75.1410039220692; Sat, 06 Sep 2014 14:33:40 -0700 (PDT) Received: by 10.112.126.137 with HTTP; Sat, 6 Sep 2014 14:33:40 -0700 (PDT) In-Reply-To: References: Date: Sat, 6 Sep 2014 14:33:40 -0700 Message-ID: Subject: Re: question about incremental backup and cluster replication From: Suraj Varma To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a1134652ede6cc005026c560c X-Virus-Checked: Checked by ClamAV on apache.org --001a1134652ede6cc005026c560c Content-Type: text/plain; charset=UTF-8 The answer to "can they solve your problem" is "yes". For "how to do this", start reading about your options here so you can pick what works best for your need (and your version of hbase): http://hbase.apache.org/book/ops.backup.html (and links out of this page) http://hbase.apache.org/book/ops.snapshots.html and HBase Backups from HBaseCon 2014: http://www.slideshare.net/HBaseCon/operations-session-5-35938493 http://vimeo.com/98359049 --Suraj On Thu, Sep 4, 2014 at 9:11 PM, Li Li wrote: > hi all, > in my application, most of the time, we do not write to hbase but > only read. Every a few hours(or even a day), We do a lot of write > operations to hbase intensively. To avoid data lost, we also want > backup our data every day(or week) > I know hbase has advanced features like backup and cluster > replication. can they solve my problem? > If I am using traditional rdbms like mysql, I will use > master/slaves cluster. master only service write requests and slave > service read requests. Because my application do not need real time > feature, So I can tolerant latency. For data safety, I can monthly > full backup all data and incremental backup every day. > How can I do this in hbase? > --001a1134652ede6cc005026c560c--