From ab5c0a37ae4665c2f203911aa65eac509ec3703b Mon Sep 17 00:00:00 2001 From: distix ticketing system Date: Mon, 31 Jul 2017 15:30:19 +0000 Subject: imported mails --- .../Maildir/new/1501515019.M474587P5467Q1.koom | 96 ++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 tickets/eea0e58a8b7a4b0b985b21046e139ccc/Maildir/new/1501515019.M474587P5467Q1.koom diff --git a/tickets/eea0e58a8b7a4b0b985b21046e139ccc/Maildir/new/1501515019.M474587P5467Q1.koom b/tickets/eea0e58a8b7a4b0b985b21046e139ccc/Maildir/new/1501515019.M474587P5467Q1.koom new file mode 100644 index 0000000..7708490 --- /dev/null +++ b/tickets/eea0e58a8b7a4b0b985b21046e139ccc/Maildir/new/1501515019.M474587P5467Q1.koom @@ -0,0 +1,96 @@ +Return-Path: +X-Original-To: distix@pieni.net +Delivered-To: distix@pieni.net +Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221]) + by pieni.net (Postfix) with ESMTPS id EABC641176 + for ; Mon, 31 Jul 2017 15:28:10 +0000 (UTC) +Received: from platypus.pepperfish.net (unknown [10.112.101.20]) + by yaffle.pepperfish.net (Postfix) with ESMTP id B5A8D417D3; + Mon, 31 Jul 2017 16:28:10 +0100 (BST) +Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1dcCc6-0001G5-Mu; Mon, 31 Jul 2017 16:28:10 +0100 +Received: from [10.112.101.21] (helo=mx3.pepperfish.net) + by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian)) + id 1dcCc5-0001Fl-57 + for ; Mon, 31 Jul 2017 16:28:09 +0100 +Received: from mail.dasr.de ([217.69.77.164]) + by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) + (Exim 4.89) (envelope-from ) id 1dcCc3-0003wA-BB + for obnam-support@obnam.org; Mon, 31 Jul 2017 16:28:09 +0100 +Received: from p5ddf99ae.dip0.t-ipconnect.de ([93.223.153.174] + helo=chu.walfield.org) + by mail.dasr.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) + (Exim 4.86_2) (envelope-from ) + id 1dcCbx-00030G-Oz; Mon, 31 Jul 2017 15:28:01 +0000 +Date: Mon, 31 Jul 2017 17:28:01 +0200 +Message-ID: <87r2wwhbi6.wl-neal@walfield.org> +From: "Neal H. Walfield" +To: Lars Wirzenius +In-Reply-To: <20170729131625.rvfvel7d5vrl7hoo@liw.fi> +References: <87mv7nty3v.wl-neal@walfield.org> + <20170729131625.rvfvel7d5vrl7hoo@liw.fi> +User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) + FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/25.1 + (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) +MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") +Content-Type: text/plain; charset=US-ASCII +X-Pepperfish-Transaction: 7d84-1c01-0833-ccb2 +X-Spam-Score: -2.4 +X-Spam-Score-int: -23 +X-Spam-Bar: -- +X-Scanned-By: pepperfish.net, Mon, 31 Jul 2017 16:28:09 +0100 +X-Spam-Report: Content analysis details: (-2.4 points) + pts rule name description + ---- ---------------------- -------------------------------------------------- + -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no + trust [217.69.77.164 listed in list.dnswl.org] + -0.5 PPF_USER_AGENT User-Agent: exists + -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% + [score: 0.0000] +X-ACL-Warn: message may be spam +X-Scan-Signature: dec02e0749d215982dbb7ebe51425d50 +Cc: obnam-support +Subject: Re: Backups of backups +X-BeenThere: obnam-support@obnam.org +X-Mailman-Version: 2.1.5 +Precedence: list +List-Id: Obnam backup software discussion +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +Sender: obnam-support-bounces@obnam.org +Errors-To: obnam-support-bounces@obnam.org + +On Sat, 29 Jul 2017 15:16:25 +0200, +Lars Wirzenius wrote: +> > My current backup of backup solution is to use 'zfs send' to replicate +> > my backup to an offsite location. This works great, but has the +> > limitation that the offsite server has to have the same amount of disk +> > space as the onsite server. +> > +> > Does obnam have any support for backups of backups? For instance, I +> > think it would be cool to just propagate a particular generation? +> > Then, my offsite backup might only have the last few backups, but the +> > onsite backup could keep a longer history. +> +> Obnam doesn't support that. If you want to have backups in two +> locations, why not run Obnam twice, once per location? + +Unfortunately, it is cheap to send data, but expensive to read it. If +I correctly understand how obnam works, then obnam does a lot of +reading to compare data even if nothing has changed. (If that's not +true, then please correct me!) + +Thanks! + +:) Neal + +_______________________________________________ +obnam-support mailing list +obnam-support@obnam.org +http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org -- cgit v1.2.1