1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
|
Return-Path: <obnam-dev-bounces@obnam.org>
X-Original-To: distix@pieni.net
Delivered-To: distix@pieni.net
Received: from bagpuss.pepperfish.net (bagpuss.pepperfish.net [148.251.8.16])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pieni.net (Postfix) with ESMTPS id 097EB2CDF2
for <distix@pieni.net>; Fri, 26 Feb 2016 09:51:25 +0100 (CET)
Received: from platypus.pepperfish.net (unknown [10.112.100.20])
by bagpuss.pepperfish.net (Postfix) with ESMTP id 48A75CBF;
Fri, 26 Feb 2016 08:51:23 +0000 (GMT)
Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1aZE7P-0000zA-4w; Fri, 26 Feb 2016 08:51:23 +0000
Received: from inmail0 ([10.112.100.10] helo=mx0.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1aZE7N-0000yt-In
for <obnam-dev@obnam.org>; Fri, 26 Feb 2016 08:51:21 +0000
Received: from upsilon.cc ([178.32.142.91])
by mx0.pepperfish.net with esmtp (Exim 4.80)
(envelope-from <zack@upsilon.cc>) id 1aZE7L-0005G4-HO
for obnam-dev@obnam.org; Fri, 26 Feb 2016 08:51:21 +0000
Received: from timira.takhisis.invalid (dt-65050.paris.inria.fr [128.93.65.50])
by upsilon.cc (Postfix) with ESMTPSA id 7CB93100A4
for <obnam-dev@obnam.org>; Fri, 26 Feb 2016 09:51:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=upsilon.cc; s=mail;
t=1456476664; bh=QisMNMDu9SLg1gRzQhcp75LRPHeFJIAr2rt+1cWU5lc=;
h=Date:From:To:Subject:From;
b=S7yzVPaorIItQcwnbsCsUskptsw7+JVcdxNOdtPqmF70BncnyUwu1HFUOBJ1N4EXE
vUAsDIVkTng2JqjeRTMuu8nc3enxFj57ggx7I19gtjIfxCd1pChMDVbCp491qubjt9
3XmWyljBcngDLrcvnvE6RrZNH1TtTqKHxnmsPQhA=
Received: by timira.takhisis.invalid (Postfix, from userid 1000)
id 509606012A; Fri, 26 Feb 2016 09:51:04 +0100 (CET)
Date: Fri, 26 Feb 2016 09:51:04 +0100
From: Stefano Zacchiroli <zack@upsilon.cc>
To: obnam-dev@obnam.org
Message-ID: <20160226085104.GA11872@upsilon.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Spam-Score: -3.5
X-Spam-Score-int: -34
X-Spam-Bar: ---
X-Scanned-By: pepperfish.net, Fri, 26 Feb 2016 08:51:21 +0000
X-Spam-Report: Content analysis details: (-3.5 points)
pts rule name description
---- ---------------------- --------------------------------------------------
-1.0 PPF_USER_AGENT_MUTT User-Agent: contains Mutt (Mutt isn't a spam
tool) -0.5 PPF_USER_AGENT User-Agent: exists
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-ACL-Warn: message may be spam
X-Scan-Signature: 2c50e0cfd6ac8342e87940d191065d4f
Subject: injecting old backup generations
X-BeenThere: obnam-dev@obnam.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Obnam development discussions <obnam-dev-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-dev-obnam.org>
List-Post: <mailto:obnam-dev@obnam.org>
List-Help: <mailto:obnam-dev-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org>,
<mailto:obnam-dev-request@obnam.org?subject=subscribe>
Sender: obnam-dev-bounces@obnam.org
Errors-To: obnam-dev-bounces@obnam.org
[ forwarding here a discussion started with Lars on IRC ]
Hi all,
in migrating backup solutions to obnam, I've stumbled upon a use case
that is not very well supported by obnam today: injecting old backups
(say, ~5 years of history) as retrofitted obnam backup generations. That
is a requirement in many cases, as you don't want to be forced to use
different tools---obnam or your previous solution---depending on the age
of the backup you want to explore.
There are at least two problems to support this use case:
a) faking paths: I want to be able to extract old backups in some dir,
and tell obnam to backup those dirs as if they were the root dir
(this is to avoid inconsistent path access when exploring pre-obnam
backups and post-obnam ones)
b) faking timestamps: once extracted old backups, I want to inject them
telling obnam "consider this backup as dated $TIMESTAMP"
Regarding (a), it ties to a more generally wanted obnam feature, i.e.,
the ability to mangle paths. I was considering that (a) could be
implemented by adding some sort of chroot support into obnam, but Lars
told me he is pondering a more general "path mangling" support for
obnam. Any pointers to the current status (spec, design, code) of that?
Regarding (b), I haven't tried myself but I've been told that faketime
works just fine. So that might be a way around this issue. OTOH the
question remains of whether obnam would welcome to have a more specific
"time override" flag as part of its native features.
Also, there is the question of whether people would prefer adding two
separate knobs that allow to do (a) and (b) independently, or rather add
a high-level "inject old backup" feature.
I'd love to hear your thoughts on this matter!
Cheers.
--
Stefano Zacchiroli . . . . . . . zack@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »
_______________________________________________
obnam-dev mailing list
obnam-dev@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-dev-obnam.org
|
