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
|
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 2813041294
for <distix@pieni.net>; Sat, 29 Jul 2017 08:58:48 +0000 (UTC)
Received: from platypus.pepperfish.net (unknown [10.112.101.20])
by yaffle.pepperfish.net (Postfix) with ESMTP id 65666418DD;
Sat, 29 Jul 2017 09:58:47 +0100 (BST)
Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
id 1dbNaB-0002PU-C3; Sat, 29 Jul 2017 09:58:47 +0100
Received: from [10.112.101.21] (helo=mx3.pepperfish.net)
by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
id 1dbNa9-0002PI-O5
for <obnam-support@obnam.org>; Sat, 29 Jul 2017 09:58:45 +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 <neal@walfield.org>) id 1dbNa7-0001oe-U9
for obnam-support@obnam.org; Sat, 29 Jul 2017 09:58:45 +0100
Received: from p5ddf936e.dip0.t-ipconnect.de ([93.223.147.110]
helo=grit.huenfield.org.walfield.org)
by mail.dasr.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.86_2) (envelope-from <neal@walfield.org>) id 1dbNZz-0006Wg-Hy
for obnam-support@obnam.org; Sat, 29 Jul 2017 08:58:35 +0000
Date: Sat, 29 Jul 2017 10:58:34 +0200
Message-ID: <87o9s3ty9x.wl-neal@walfield.org>
From: "Neal H. Walfield" <neal@walfield.org>
To: obnam-support <obnam-support@obnam.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/24.5
(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: bccb-2509-a976-843d
X-Spam-Score: -2.4
X-Spam-Score-int: -23
X-Spam-Bar: --
X-Scanned-By: pepperfish.net, Sat, 29 Jul 2017 09:58:45 +0100
X-Spam-Report: Content analysis details: (-2.4 points)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.5 PPF_USER_AGENT User-Agent: exists
-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]
-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: bdc2be5dc634686df142fe367da3f314
Subject: 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>
Sender: obnam-support-bounces@obnam.org
Errors-To: obnam-support-bounces@obnam.org
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
|
