unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: myglc2 <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: backup w/ duplicity borg attic bup?
Date: Wed, 10 May 2017 18:15:04 -0400	[thread overview]
Message-ID: <20170510221504.GA2427@jasmine> (raw)
In-Reply-To: <8660h8h4lb.fsf@gmail.com>

On Wed, May 10, 2017 at 03:52:32PM -0400, myglc2 wrote:
> I am looking for a command line de-duplicating backup tool. I will be
> using it between GuixSD, Guix/GNU/Linux, and MacOS.
> 
> Based on what I see in gnu/packages/backup.scm and in https://brew.sh,
> duplicity, borg and attic seem like they could be good choices.

I don't think Attic is a good choice anymore; it's unmaintained for ~2
years and has critical data integrity and security bugs. Borg is the
active fork. The Borg team is developing new features while also
triaging the Attic bug tracker, although they've worked through most of
those Attic bugs by now:

https://github.com/borgbackup/borg/issues/5

I like Borg overall. I've restored from it many times now, and it's
always worked. The developers are actively maintaining and improving the
software, and there is even a commercial offering (rsync.net). It's a
very similar backup paradigm to Tarsnap (snapshots composed of
deduplicated encrypted chunks), although the key management is less
advanced.

I'm not familiar with Duplicity so I can't compare it to Borg.

  parent reply	other threads:[~2017-05-10 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 19:52 backup w/ duplicity borg attic bup? myglc2
2017-05-10 20:27 ` Arun Isaac
2017-05-10 22:15 ` Leo Famulari [this message]
2017-05-11  8:23 ` Alex Sassmannshausen
  -- strict thread matches above, loose matches on Subject: below --
2017-05-11  4:46 André

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170510221504.GA2427@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=myglc2@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).