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 593EC200D2D for ; Fri, 27 Oct 2017 09:06:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 57CC7160BF6; Fri, 27 Oct 2017 07:06:05 +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 A02AC160BDC for ; Fri, 27 Oct 2017 09:06:04 +0200 (CEST) Received: (qmail 347 invoked by uid 500); 27 Oct 2017 07:06:03 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 280 invoked by uid 99); 27 Oct 2017 07:06:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Oct 2017 07:06:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A80E1180803 for ; Fri, 27 Oct 2017 07:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 1J_kkz3EF90s for ; Fri, 27 Oct 2017 07:06:02 +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 5AB295FCD4 for ; Fri, 27 Oct 2017 07:06:01 +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 977E9E0EF0 for ; Fri, 27 Oct 2017 07:06:00 +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 376F9212FA for ; Fri, 27 Oct 2017 07:06:00 +0000 (UTC) Date: Fri, 27 Oct 2017 07:06:00 +0000 (UTC) From: "Amit Kabra (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-19106) Backup self validation for its correctness. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 27 Oct 2017 07:06:05 -0000 Amit Kabra created HBASE-19106: ---------------------------------- Summary: Backup self validation for its correctness. Key: HBASE-19106 URL: https://issues.apache.org/jira/browse/HBASE-19106 Project: HBase Issue Type: Bug Reporter: Amit Kabra Backups are critical and if they don't work when we need them at the time of restore than they are not useful. We should do sanity test for each backup job we run that it is restorable and hence can be trusted. A self validation feature can be added for the same to the backups where whenever a backup is run , once it finishes it will trigger a validation job that will do a sample restoration of the backed up data and will make sure that it compares well with actual data. -- This message was sent by Atlassian JIRA (v6.4.14#64029)