Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 655EB200D39 for ; Sat, 11 Nov 2017 23:58:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 63E09160C03; Sat, 11 Nov 2017 22:58:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AABF41609E5 for ; Sat, 11 Nov 2017 23:58:06 +0100 (CET) Received: (qmail 53556 invoked by uid 500); 11 Nov 2017 22:58:05 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 53545 invoked by uid 99); 11 Nov 2017 22:58:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Nov 2017 22:58:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 02B8FDA889 for ; Sat, 11 Nov 2017 22:58:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3LFbI9pkwmK0 for ; Sat, 11 Nov 2017 22:58:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B04735FBB1 for ; Sat, 11 Nov 2017 22:58:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4B7CDE0617 for ; Sat, 11 Nov 2017 22:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 94ACB240CE for ; Sat, 11 Nov 2017 22:58:00 +0000 (UTC) Date: Sat, 11 Nov 2017 22:58:00 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16574) Add backup / restore feature to refguide MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 11 Nov 2017 22:58:07 -0000 [ https://issues.apache.org/jira/browse/HBASE-16574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248716#comment-16248716 ] stack commented on HBASE-16574: ------------------------------- Did these get addressed? {code} Nit: On usage, the backupid exists nowhere in the system except as output from the backup command? Later it is explained what it is which is helpful. Also, later again it is explained that it does live as part of the backup history. Could be good to call out these facts earlier. Could also say how long a backup is going to take roughly. Me as an operator would be afraid to run a backup because I'd think the command could run for ever on my 100 node cluster. Reading later in the manual, it seems that it could start and return immediately and then I check in on status. Would be good to surface some of that up here at start of doc. to allay the fears of the poor operator. {code} > Add backup / restore feature to refguide > ---------------------------------------- > > Key: HBASE-16574 > URL: https://issues.apache.org/jira/browse/HBASE-16574 > Project: HBase > Issue Type: Improvement > Reporter: Ted Yu > Assignee: Frank Welsch > Labels: backup > Fix For: 2.0.0-beta-1 > > Attachments: B&R command-line tools and configuration (updated).pdf, Backup-and-Restore-Apache_19Sep2016.pdf, HBASE-16574.001.patch, HBASE-16574.002.patch, HBASE-16574.003.branch-2.patch, hbase-book-16574.003.pdf, hbase_reference_guide.v1.pdf > > > This issue is to add backup / restore feature description to hbase refguide. > The description should cover: > scenarios where backup / restore is used > backup / restore commands and sample usage > considerations in setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)