summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authordistix ticketing system <distix@pieni.net>2017-06-23 19:20:24 +0000
committerdistix ticketing system <distix@pieni.net>2017-06-23 19:20:24 +0000
commit8355a0482f0ecabc2ce955072ebc231f31d4f5bc (patch)
tree24a72ebc5162c306db42c5ae2e50a6438699be1d
parentbfd7a85f4e94deb8d82c026fcff47d85874b7ab5 (diff)
downloadobnam-support-distix-8355a0482f0ecabc2ce955072ebc231f31d4f5bc.tar.gz
imported mails
-rw-r--r--tickets/225024dd755641a39bfe899d72ee6b74/Maildir/cur/.this-dir-not-empty/.empty/empty-file0
-rw-r--r--tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/.this-dir-not-empty/.empty/empty-file0
-rw-r--r--tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/1498245624.M117824P23311Q1.koom108
-rw-r--r--tickets/225024dd755641a39bfe899d72ee6b74/Maildir/tmp/.this-dir-not-empty/.empty/empty-file0
-rw-r--r--tickets/225024dd755641a39bfe899d72ee6b74/ticket.yaml6
5 files changed, 114 insertions, 0 deletions
diff --git a/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/cur/.this-dir-not-empty/.empty/empty-file b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/cur/.this-dir-not-empty/.empty/empty-file
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/cur/.this-dir-not-empty/.empty/empty-file
diff --git a/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/.this-dir-not-empty/.empty/empty-file b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/.this-dir-not-empty/.empty/empty-file
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/.this-dir-not-empty/.empty/empty-file
diff --git a/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/1498245624.M117824P23311Q1.koom b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/1498245624.M117824P23311Q1.koom
new file mode 100644
index 0000000..1dea61b
--- /dev/null
+++ b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/new/1498245624.M117824P23311Q1.koom
@@ -0,0 +1,108 @@
+Return-Path: <obnam-support-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])
+ by pieni.net (Postfix) with ESMTPS id 0414343CCB
+ for <distix@pieni.net>; Fri, 23 Jun 2017 19:19:01 +0000 (UTC)
+Received: from platypus.pepperfish.net (unknown [10.112.100.20])
+ by bagpuss.pepperfish.net (Postfix) with ESMTP id 8F214BCD;
+ Fri, 23 Jun 2017 20:19:01 +0100 (BST)
+Received: from ip6-localhost ([::1] helo=platypus.pepperfish.net)
+ by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
+ id 1dOU6f-0006lz-FB; Fri, 23 Jun 2017 20:19:01 +0100
+Received: from yaffle.pepperfish.net ([88.99.213.221]
+ helo=inmail2.pepperfish.net)
+ by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
+ id 1dOU6e-0006ld-MS
+ for <obnam-support@obnam.org>; Fri, 23 Jun 2017 20:19:00 +0100
+Received: from einhorn-mail.in-berlin.de ([217.197.80.20])
+ by inmail2.pepperfish.net with esmtps
+ (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89)
+ (envelope-from <Michael@heidecker.net>) id 1dOU6d-0007Uw-3u
+ for obnam-support@obnam.org; Fri, 23 Jun 2017 20:19:00 +0100
+X-Envelope-From: Michael@heidecker.net
+X-Envelope-To: <obnam-support@obnam.org>
+Received: from [192.168.88.30] (p508EA41E.dip0.t-ipconnect.de [80.142.164.30])
+ (authenticated bits=0)
+ by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id
+ v5NJInJR003149
+ (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
+ for <obnam-support@obnam.org>; Fri, 23 Jun 2017 21:18:50 +0200
+To: obnam-support@obnam.org
+From: Michael Heidecker <Michael@heidecker.net>
+Message-ID: <4a966e07-e14a-7cf7-c8d0-ee1ad283a180@heidecker.net>
+Date: Fri, 23 Jun 2017 21:18:49 +0200
+User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
+ Thunderbird/52.1.1
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Transfer-Encoding: 7bit
+Content-Language: en-US
+X-Pepperfish-Transaction: a7e0-be8b-8c49-90a0
+X-Spam-Score: -3.1
+X-Spam-Score-int: -30
+X-Spam-Bar: ---
+X-Scanned-By: pepperfish.net, Fri, 23 Jun 2017 20:19:00 +0100
+X-Spam-Report: Content analysis details: (-3.1 points)
+ pts rule name description
+ ---- ---------------------- --------------------------------------------------
+ -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
+ trust [217.197.80.20 listed in list.dnswl.org]
+ -0.5 PPF_USER_AGENT User-Agent: exists
+ -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: 909e24a621a695a51ad00ecc17e68015
+Subject: Two step backup strategy?
+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
+
+I am trying to setup a new backup strategy and looking at obnam as the
+tool for helping me.
+
+Since my upload speed to internet is slow, I want to backup my clients
+first to my Synology NAS (fast) which in turn backups everything into
+the cloud automatically.
+
+What would be the best way to do the backup?
+
+(1) Backup the desktop to the NAS with obnam and this backup again with
+obnam to the cloud
+
+(2) Backup the desktop to the NAS with obnam and rsync the obnam backup
+to the cloud
+
+(3) Backup the desktop to the NAS with rsync and use obnam to backup
+this backup the cloud
+
+(4) ???
+
+Since the CPU on the NAS is slow, the preferably first backup should
+include encryption.
+
+One way to achieve this is to encfs in reverse mode to generate an
+encrypted view of my locally unencrypted /home/user directory besides
+the obnam built-in encrpytion. Would this work? (I have some encfs
+encrypted directories on some machines as well which I intent to backup
+in encrypted state directly)
+
+Thanks
+
+Michael
+
+
+_______________________________________________
+obnam-support mailing list
+obnam-support@obnam.org
+http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/obnam-support-obnam.org
diff --git a/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/tmp/.this-dir-not-empty/.empty/empty-file b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/tmp/.this-dir-not-empty/.empty/empty-file
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/tickets/225024dd755641a39bfe899d72ee6b74/Maildir/tmp/.this-dir-not-empty/.empty/empty-file
diff --git a/tickets/225024dd755641a39bfe899d72ee6b74/ticket.yaml b/tickets/225024dd755641a39bfe899d72ee6b74/ticket.yaml
new file mode 100644
index 0000000..6f64c50
--- /dev/null
+++ b/tickets/225024dd755641a39bfe899d72ee6b74/ticket.yaml
@@ -0,0 +1,6 @@
+status:
+- ''
+ticket-id:
+- 225024dd755641a39bfe899d72ee6b74
+title:
+- Two step backup strategy?