From 598a6abe986ed30fbc15267b090fddf4ef36a214 Mon Sep 17 00:00:00 2001 From: distix ticketing system Date: Mon, 31 Jul 2017 15:16:45 +0000 Subject: imported mails --- .../Maildir/new/1501514205.M62304P2495Q1.koom | 125 +++++++++++++++++++++ 1 file changed, 125 insertions(+) create mode 100644 tickets/c14ec422d4d74aaca6dd36ea1905dced/Maildir/new/1501514205.M62304P2495Q1.koom diff --git a/tickets/c14ec422d4d74aaca6dd36ea1905dced/Maildir/new/1501514205.M62304P2495Q1.koom b/tickets/c14ec422d4d74aaca6dd36ea1905dced/Maildir/new/1501514205.M62304P2495Q1.koom new file mode 100644 index 0000000..ef2bda2 --- /dev/null +++ b/tickets/c14ec422d4d74aaca6dd36ea1905dced/Maildir/new/1501514205.M62304P2495Q1.koom @@ -0,0 +1,125 @@ +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 E222243620 + for ; Mon, 31 Jul 2017 15:12:56 +0000 (UTC) +Received: from platypus.pepperfish.net (unknown [10.112.101.20]) + by yaffle.pepperfish.net (Postfix) with ESMTP id 5702F417AB; + Mon, 31 Jul 2017 16:12:56 +0100 (BST) +Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net) + by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) + id 1dcCNM-0007ml-Ad; Mon, 31 Jul 2017 16:12:56 +0100 +Received: from [10.112.101.21] (helo=mx3.pepperfish.net) + by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian)) + id 1dcCNK-0007mR-Rp + for ; Mon, 31 Jul 2017 16:12:54 +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 1dcCNH-0003c9-DG + for obnam-support@obnam.org; Mon, 31 Jul 2017 16:12:54 +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 1dcCN8-0002pt-CC; Mon, 31 Jul 2017 15:12:42 +0000 +Date: Mon, 31 Jul 2017 17:12:34 +0200 +Message-ID: <87vam8hc7x.wl-neal@walfield.org> +From: "Neal H. Walfield" +To: SanskritFritz +In-Reply-To: +References: <87o9s3ty9x.wl-neal@walfield.org> + +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: 45fb-e31b-b787-2e24 +X-Spam-Score: -2.4 +X-Spam-Score-int: -23 +X-Spam-Bar: -- +X-Scanned-By: pepperfish.net, Mon, 31 Jul 2017 16:12:54 +0100 +X-Spam-Report: Content analysis details: (-2.4 points) + pts rule name description + ---- ---------------------- -------------------------------------------------- + -0.5 PPF_USER_AGENT User-Agent: exists + -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% + [score: 0.0000] + -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] +X-ACL-Warn: message may be spam +X-Scan-Signature: ce9efb50043e98c3e6c2276a1343ad7d +Cc: obnam-support +Subject: Re: Migrating old backups to obnam +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 13:12:48 +0200, +SanskritFritz wrote: +> Why insist on having only one repo? You could reserve a separate repo for the old backups. + +That's true. But, it would waste about a TB of space :/. + +> On Sat, Jul 29, 2017 at 10:58 AM, Neal H. Walfield wrote: +> +> Hi, +> +> I'm transitioning to obnam. (I've actually been using it for about +> three or four years in a smaller backup solution, and I've been quite +> happy with it. Thanks!) +> +> I'd like to add my old backups to my obnam repository. Unfortunately, +> the meta-data is going to be wrong in several places: +> +> - The time of the backup will be the current time. My tests suggest +> that using faketime tricks obnam at least with respect to 'obnam +> generations', but perhaps there are other places where this might +> be a problem. +> +> - The absolute path will be wrong. That is, I normally backup +> /home, but I don't want to restore by old backups to /home, +> because I need to keep using my NAS during the migration :). Is +> there a way to fake the path so that obnam ls show /home instead +> of /restore? +> +> (Actually, I backup /home/.zfs/snapshots/backup and would prefer +> that it show up as /home in the backup. But this is a variant of +> the same problem.) +> +> - Generations will be "out of order". I imagine this could be a +> problem with respect to aging. For instance, if obnam assumes +> that a numerically larger generation is necessarily younger. Is +> something like this the case? If so, then I guess the simpliest +> solution is to migrate the backups in order. +> +> Thanks! +> +> :) Neal +> +> _______________________________________________ +> obnam-support mailing list +> obnam-support@obnam.org +> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org +> +> [2 ] +> _______________________________________________ +> obnam-support mailing list +> obnam-support@obnam.org +> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org + +_______________________________________________ +obnam-support mailing list +obnam-support@obnam.org +http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org -- cgit v1.2.1