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 98E49200CD0 for ; Tue, 25 Jul 2017 19:31:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 978801672AD; Tue, 25 Jul 2017 17:31:04 +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 DBE1B1672AB for ; Tue, 25 Jul 2017 19:31:03 +0200 (CEST) Received: (qmail 55848 invoked by uid 500); 25 Jul 2017 17:31:03 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 55839 invoked by uid 99); 25 Jul 2017 17:31:03 -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; Tue, 25 Jul 2017 17:31:03 +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 98002C0A20 for ; Tue, 25 Jul 2017 17:31:02 +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 JEcyFdSbiIzS for ; Tue, 25 Jul 2017 17:31:01 +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 389815FDBF for ; Tue, 25 Jul 2017 17:31: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 8C027E00A2 for ; Tue, 25 Jul 2017 17:31: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 3FA9C21EE3 for ; Tue, 25 Jul 2017 17:31:00 +0000 (UTC) Date: Tue, 25 Jul 2017 17:31:00 +0000 (UTC) From: "Fred Krone (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (GEODE-3298) Add timestamps to backups to allow for incremental recovery MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 25 Jul 2017 17:31:04 -0000 [ https://issues.apache.org/jira/browse/GEODE-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone updated GEODE-3298: ------------------------------ Issue Type: Sub-task (was: Improvement) Parent: GEODE-3161 > Add timestamps to backups to allow for incremental recovery > ----------------------------------------------------------- > > Key: GEODE-3298 > URL: https://issues.apache.org/jira/browse/GEODE-3298 > Project: Geode > Issue Type: Sub-task > Components: persistence > Reporter: Fred Krone > > Scenario: right now when you do an incremental backup it adds to the previous backup. This means you have one growing backup file to recover from and no option to ever recover from a different point-in-time. It would be nice to allow an option to backup and recover from different points in-time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)