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
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
|
Return-Path: <obnam-support-bounces@obnam.org>
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 E59BF42E79
for <distix@pieni.net>; Sat, 29 Jul 2017 11:13:39 +0000 (UTC)
Received: from platypus.pepperfish.net (unknown [10.112.101.20])
by yaffle.pepperfish.net (Postfix) with ESMTP id 9F0E2418D4;
Sat, 29 Jul 2017 12:13:39 +0100 (BST)
Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1dbPgh-0000jF-K4; Sat, 29 Jul 2017 12:13:39 +0100
Received: from [10.112.101.21] (helo=mx3.pepperfish.net)
by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
id 1dbPgg-0000iu-3v
for <obnam-support@obnam.org>; Sat, 29 Jul 2017 12:13:38 +0100
Received: from mail-qt0-f180.google.com ([209.85.216.180])
by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
(Exim 4.89) (envelope-from <sanskritfritz@gmail.com>)
id 1dbPge-0003sY-3E
for obnam-support@obnam.org; Sat, 29 Jul 2017 12:13:38 +0100
Received: by mail-qt0-f180.google.com with SMTP id a18so72108258qta.0
for <obnam-support@obnam.org>; Sat, 29 Jul 2017 04:13:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=zbD/p64WwB1ihRBrhvOAV67hH4YaHWkDubtaylMw6g0=;
b=rnVokdfERvmGCgRnQ7gw9zLQioHJSplTqAXjf6W1fKj0awgRqiOfDKALkOq9sc8pdE
GMHWsmcIqHapTzCKuZrsDsR+23XeImG4Q/TZWT4uh9ElcvcyZmzHAcPytk1p+GP6tlmz
AKG3n46mljG4LUyr8BYQSlsDK3Az2r9UcDjMHl6EaSGBP9y+BC3TZf5zVPfMxxp+98Ao
dftCUPpJs8j0yGYlTZlFmLmWHYp8piIqr7xYEtMXjSn04pHWl7IHADIqB5w631ZXgTKp
GZC1AsyM4+R0EnbURhsP65fnLi76MdRU6D2Gvsvz1wadm9PYC0jxkRyehrQ+YZUdxFdE
ia2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=zbD/p64WwB1ihRBrhvOAV67hH4YaHWkDubtaylMw6g0=;
b=D1XrInw3T0y/KpDGSzENTHcYJfrHYQZtvDYkhy2jQLlb8wZyeerPnRl6k/s1tPxPXa
SykAKXi/w81OraVB6lavM6cYMdwLwRfUGZbsu+6BrTSotKqXNzxN1Z6xff9SIRpA1UXm
9AMUPN66tzgv5I9A+Cg5/dEvZA3heieN8ae/ii0Ggfu2iEEgshObvNyr78cekW9parSd
XvDcmvlsTS9drR8UkLAI1ldxglF1ZdTnoS9EPi3K5+wRpx3DYSlQWWUO53wy5lnPREEz
mHc+660Wjhr1EQi4RTYKbrp01eNbREPxKX/Qni3lwuoS6Yqj/1rzMYanEG2MatsXPGJi
FAXQ==
X-Gm-Message-State: AIVw110s9ifLyz6xFZWFR+2wf3b7ybIkII59EeZMP7vmeBygrTI//WZP
hZkoXekLp288DVlhrdI4Q67VWxS4/w==
X-Received: by 10.200.0.65 with SMTP id i1mr15114776qtg.193.1501326809094;
Sat, 29 Jul 2017 04:13:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.38.35 with HTTP; Sat, 29 Jul 2017 04:12:48 -0700 (PDT)
In-Reply-To: <87o9s3ty9x.wl-neal@walfield.org>
References: <87o9s3ty9x.wl-neal@walfield.org>
From: SanskritFritz <sanskritfritz@gmail.com>
Date: Sat, 29 Jul 2017 13:12:48 +0200
Message-ID: <CAExbbMzyX8Fhbsn8HNFn_dOp5j_j=87Gv9m1mUmg_Dv+u3_xLA@mail.gmail.com>
To: "Neal H. Walfield" <neal@walfield.org>
X-Pepperfish-Transaction: f394-a228-9497-2981
X-Spam-Score: 3.2
X-Spam-Score-int: 32
X-Spam-Bar: +++
X-Scanned-By: pepperfish.net, Sat, 29 Jul 2017 12:13:38 +0100
X-Spam-Report: Content analysis details: (3.2 points)
pts rule name description
---- ---------------------- --------------------------------------------------
0.5 PPF_RECEIVED_HTTP Received header mentions http
1.0 PPF_FROM_CONTAINS_MAIL The From header contains 'mail'
0.2 PPF_ALTERNATIVES Body in multipart/alternative
1.2 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(sanskritfritz[at]gmail.com)
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.3 HTML_MESSAGE BODY: HTML included in message
0.2 PPF_NUMERIC_ENTITY RAW: Body contains numeric HTML entities
1.0 PPF_BLANK RAW: Body contains _blank
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)
[209.85.216.180 listed in wl.mailspike.net]
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust [209.85.216.180 listed in list.dnswl.org]
1.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source
[209.85.216.180 listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
X-ACL-Warn: message may be spam
X-Scan-Signature: ba65ac4f16e3e41acb4ab9088f872dd0
Cc: obnam-support <obnam-support@obnam.org>
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 <obnam-support-obnam.org>
List-Unsubscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
<mailto:obnam-support-request@obnam.org?subject=unsubscribe>
List-Archive: <http://listmaster.pepperfish.net/pipermail/obnam-support-obnam.org>
List-Post: <mailto:obnam-support@obnam.org>
List-Help: <mailto:obnam-support-request@obnam.org?subject=help>
List-Subscribe: <http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org>,
<mailto:obnam-support-request@obnam.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6139220883091248204=="
Mime-version: 1.0
Sender: obnam-support-bounces@obnam.org
Errors-To: obnam-support-bounces@obnam.org
--===============6139220883091248204==
Content-Type: multipart/alternative; boundary="f403045ee68e25e04d055572e361"
--f403045ee68e25e04d055572e361
Content-Type: text/plain; charset="UTF-8"
Why insist on having only one repo? You could reserve a separate repo for
the old backups.
On Sat, Jul 29, 2017 at 10:58 AM, Neal H. Walfield <neal@walfield.org>
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/ob
> nam-support-obnam.org
>
--f403045ee68e25e04d055572e361
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Why insist on having only one repo? You could reserve a se=
parate repo for the old backups.<br><br><br><div class=3D"gmail_extra"><br>=
<div class=3D"gmail_quote">On Sat, Jul 29, 2017 at 10:58 AM, Neal H. Walfie=
ld <span dir=3D"ltr"><<a href=3D"mailto:neal@walfield.org" target=3D"_bl=
ank">neal@walfield.org</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Hi,<br>
<br>
I'm transitioning to obnam.=C2=A0 (I've actually been using it for =
about<br>
three or four years in a smaller backup solution, and I've been quite<b=
r>
happy with it.=C2=A0 Thanks!)<br>
<br>
I'd like to add my old backups to my obnam repository.=C2=A0 Unfortunat=
ely,<br>
the meta-data is going to be wrong in several places:<br>
<br>
=C2=A0 - The time of the backup will be the current time.=C2=A0 My tests su=
ggest<br>
=C2=A0 =C2=A0 that using faketime tricks obnam at least with respect to =
9;obnam<br>
=C2=A0 =C2=A0 generations', but perhaps there are other places where th=
is might<br>
=C2=A0 =C2=A0 be a problem.<br>
<br>
=C2=A0 - The absolute path will be wrong.=C2=A0 That is, I normally backup<=
br>
=C2=A0 =C2=A0 /home, but I don't want to restore by old backups to /hom=
e,<br>
=C2=A0 =C2=A0 because I need to keep using my NAS during the migration :).=
=C2=A0 Is<br>
=C2=A0 =C2=A0 there a way to fake the path so that obnam ls show /home inst=
ead<br>
=C2=A0 =C2=A0 of /restore?<br>
<br>
=C2=A0 =C2=A0 (Actually, I backup /home/.zfs/snapshots/backup and would pre=
fer<br>
=C2=A0 =C2=A0 that it show up as /home in the backup.=C2=A0 But this is a v=
ariant of<br>
=C2=A0 =C2=A0 the same problem.)<br>
<br>
=C2=A0 - Generations will be "out of order".=C2=A0 I imagine this=
could be a<br>
=C2=A0 =C2=A0 problem with respect to aging.=C2=A0 For instance, if obnam a=
ssumes<br>
=C2=A0 =C2=A0 that a numerically larger generation is necessarily younger.=
=C2=A0 Is<br>
=C2=A0 =C2=A0 something like this the case?=C2=A0 If so, then I guess the s=
impliest<br>
=C2=A0 =C2=A0 solution is to migrate the backups in order.<br>
<br>
Thanks!<br>
<br>
:) Neal<br>
<br>
<br>
______________________________<wbr>_________________<br>
obnam-support mailing list<br>
<a href=3D"mailto:obnam-support@obnam.org" target=3D"_blank">obnam-support@=
obnam.org</a><br>
<a href=3D"http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-=
support-obnam.org" rel=3D"noreferrer" target=3D"_blank">http://listmaster.p=
epperfish.n<wbr>et/cgi-bin/mailman/listinfo/ob<wbr>nam-support-obnam.org</a=
><br>
</blockquote></div><br></div></div>
--f403045ee68e25e04d055572e361--
--===============6139220883091248204==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
obnam-support mailing list
obnam-support@obnam.org
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
--===============6139220883091248204==--
|
