From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine: incremental back-ups
Date: Thu, 4 Oct 2012 11:37:34 +0100 [thread overview]
Message-ID: <20121004113734.7e6064c9@digimed.co.uk> (raw)
In-Reply-To: <506D4811.9010009@hadt.biz>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Thu, 04 Oct 2012 10:25:53 +0200, Michael Hampicke wrote:
> I am using http://backuppc.sourceforge.net/ (in portage) which brings
> some nice features like compression, de-duplication and a web interface.
> Once configured it runs automatically.
+1 for BackupPC
> What do you use for cloud/offsite backups? I am still searching for the
> perfect solution. Requirements: backups must be encrypted, delta-sync,
> and being able to resume interrupted transfers to the offsite location.
I have a Python script that uses a combination of dar,
to create encrypted backups locally, and boto to upload them to S3. I used
duplicity some years ago and found it consumed enormous amounts of
bandwidth, more than my ISP provided at the time.
--
Neil Bothwick
If a parsley farmer is sued, can they garnish his wages?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-04 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 6:38 [gentoo-user] new machine: incremental back-ups Philip Webb
2012-10-04 8:25 ` Michael Hampicke
2012-10-04 10:37 ` Neil Bothwick [this message]
2012-10-04 11:43 ` Michael Hampicke
2012-10-04 12:53 ` Neil Bothwick
2012-10-04 10:19 ` William Kenworthy
2012-10-04 15:22 ` Paul Hartman
2012-10-04 16:58 ` Doug Hunley
2012-10-05 14:28 ` [gentoo-user] " Grant Edwards
2012-10-06 0:49 ` Philip Webb
2012-10-06 9:22 ` Helmut Jarausch
2012-10-06 11:59 ` Stefan Schmiedl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121004113734.7e6064c9@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox