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
|
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 C14A540572
for <distix@pieni.net>; Sat, 29 Jul 2017 11:07:13 +0000 (UTC)
Received: from platypus.pepperfish.net (unknown [10.112.101.20])
by yaffle.pepperfish.net (Postfix) with ESMTP id 1D447418D6;
Sat, 29 Jul 2017 12:07:13 +0100 (BST)
Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1dbPaT-0000F7-0z; Sat, 29 Jul 2017 12:07:13 +0100
Received: from [10.112.101.21] (helo=mx3.pepperfish.net)
by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
id 1dbPaR-0000Eu-US
for <obnam-support@obnam.org>; Sat, 29 Jul 2017 12:07:11 +0100
Received: from mail-qk0-f182.google.com ([209.85.220.182])
by mx3.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
(Exim 4.89) (envelope-from <sanskritfritz@gmail.com>)
id 1dbPaP-0003mU-45
for obnam-support@obnam.org; Sat, 29 Jul 2017 12:07:11 +0100
Received: by mail-qk0-f182.google.com with SMTP id d145so124040182qkc.2
for <obnam-support@obnam.org>; Sat, 29 Jul 2017 04:07:02 -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=lRc26mL92Exd/nUGtxXwiA4nHCFJs8idsr1/d+T5ins=;
b=QMQvgHMgq2JWEoTfrxhhi8ObvGi5OQpTfUSYQ36iGUha8G+xyy4zL/GWTXOB5I4TlP
Iz6yC4+uDqSWbVmUvB+pUKSs5oD3RccqwQBONscht/lpnkNCrAODwl+isiSQTPQxjEDI
fUkJHIjL7BPBGEz+0Q0TZlUnyciBWKNw+wDJMS8kD4QgjUgoIEJWggxHb44GRB0CuTTA
2MlRRJjcq0eqoHx/TvyAtVmzStC3cXlXDdENsoeIcjIbukn9vBW9gkDUG5vcmH7dnE7q
dZ2mtYlfV2Rc7QqfSsxf4yApmJ1qbOdKfG2NevqdndiTifzKr1u7sAALNGklA9g9OSOk
zBiA==
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=lRc26mL92Exd/nUGtxXwiA4nHCFJs8idsr1/d+T5ins=;
b=LGapoj/cGLxml8jmGuFnBZ0etKoU6HaIYxVdl8uCZUAGm3p6V6z6ByTwFdRwYPUhgM
FzggNmklk2nOcyulZIbdMRAVSv0qYCkzuqhLjwsSrE5jA4WpmnQkOrBx96RgCnvVnEKw
Jmfgo9uiNZEuTW8S3VHXB9ac/NAPKKO8aAWa6bH6WLXogXOV1ommmXZdd1L07gdAlJE1
CJgcLzjn+cLrdZWquslxqiGA2YyqYEqWHYcVGRshZTCpI4lVciQLIc7ghrSEc3tMzoSg
NbQU4myiafJ2y3idtGOqS2EMhv1iXVRBJsm55LY2AY3oDTo6JJB5UPZEJUTuIoWrz93l
KIAg==
X-Gm-Message-State: AIVw1139hpb4U9fCrQ8LtITlqC1UTDl4cr4uo/OvW5zf/F3JPt3KZadI
AOF3zPQizdszHRJxxGcSKn4IyV+pOA==
X-Received: by 10.55.19.152 with SMTP id 24mr13250115qkt.78.1501326421335;
Sat, 29 Jul 2017 04:07:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.38.35 with HTTP; Sat, 29 Jul 2017 04:06:20 -0700 (PDT)
In-Reply-To: <87mv7nty3v.wl-neal@walfield.org>
References: <87mv7nty3v.wl-neal@walfield.org>
From: SanskritFritz <sanskritfritz@gmail.com>
Date: Sat, 29 Jul 2017 13:06:20 +0200
Message-ID: <CAExbbMxz2cMkVnTZxZNiLKDLyThByehVnR6b1FY7ExF2kTcfrg@mail.gmail.com>
To: "Neal H. Walfield" <neal@walfield.org>
X-Pepperfish-Transaction: f09f-8cfb-1332-f3fc
X-Spam-Score: 3.9
X-Spam-Score-int: 39
X-Spam-Bar: +++
X-Scanned-By: pepperfish.net, Sat, 29 Jul 2017 12:07:11 +0100
X-Spam-Report: Content analysis details: (3.9 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.220.182 listed in wl.mailspike.net]
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no
trust [209.85.220.182 listed in list.dnswl.org]
1.5 RCVD_IN_SORBS_SPAM RBL: SORBS: sender is a spam source
[209.85.220.182 listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
X-ACL-Warn: message may be spam
X-Scan-Signature: 531f3386b8fdbaa107ddf70a0e4d95bf
Cc: obnam-support <obnam-support@obnam.org>
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 <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="===============1590371878584657343=="
Mime-version: 1.0
Sender: obnam-support-bounces@obnam.org
Errors-To: obnam-support-bounces@obnam.org
--===============1590371878584657343==
Content-Type: multipart/alternative; boundary="001a11400b06092543055572cca2"
--001a11400b06092543055572cca2
Content-Type: text/plain; charset="UTF-8"
If you had enough space on the offsite system, you can upload the whole
repo and then later you just have to incrementally rsync the difference. I
don't think Obnam sports such a feature to actually split a repo.
On Sat, Jul 29, 2017 at 11:02 AM, Neal H. Walfield <neal@walfield.org>
wrote:
> Hi,
>
> 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.
>
> Thanks!
>
> :) Neal
>
> _______________________________________________
> obnam-support mailing list
> obnam-support@obnam.org
> http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/
> obnam-support-obnam.org
>
--001a11400b06092543055572cca2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">If you had enough space on the offsite system, you can upl=
oad the whole repo and then later you just have to incrementally rsync the =
difference. I don't think Obnam sports such a feature to actually split=
a repo.<br><br><br><br><br><br><br></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Sat, Jul 29, 2017 at 11:02 AM, Neal H. Walfield=
<span dir=3D"ltr"><<a href=3D"mailto:neal@walfield.org" target=3D"_blan=
k">neal@walfield.org</a>></span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">Hi,<br>
<br>
My current backup of backup solution is to use 'zfs send' to replic=
ate<br>
my backup to an offsite location.=C2=A0 This works great, but has the<br>
limitation that the offsite server has to have the same amount of disk<br>
space as the onsite server.<br>
<br>
Does obnam have any support for backups of backups?=C2=A0 For instance, I<b=
r>
think it would be cool to just propagate a particular generation?<br>
Then, my offsite backup might only have the last few backups, but the<br>
onsite backup could keep a longer history.<br>
<br>
Thanks!<br>
<br>
:) Neal<br>
<br>
______________________________<wbr>_________________<br>
obnam-support mailing list<br>
<a href=3D"mailto:obnam-support@obnam.org">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.<wbr>net/cgi-bin/mailman/listinfo/<wbr>obnam-support-obnam.org</a=
><br>
</blockquote></div><br></div>
--001a11400b06092543055572cca2--
--===============1590371878584657343==
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
--===============1590371878584657343==--
|
