All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sree Harsha Totakura <sreeharsha@totakura.in>
To: Alphazo <alphazo@gmail.com>, Psalle <psalleetsile@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Purposely using btrfs RAID1 in degraded mode ?
Date: Thu, 7 Jan 2016 18:34:23 +0100	[thread overview]
Message-ID: <568EA19F.4040804@totakura.in> (raw)
In-Reply-To: <CAHJqNbxnB9o-UwXyLf+PvttnNOcf88FwhEep1FSkye1Etp0CTA@mail.gmail.com>

Thank you Alphazo; I have been looking for something similar for a
while, but didn't know where/what to look at.
Your pointers solve my problem.

Regards,
Sree
On 01/07/2016 02:09 PM, Alphazo wrote:
> I'm a former bup user but I switched to borgbackup
> https://borgbackup.readthedocs.org/en/stable/ which is a more active
> fork of Attic and that solves two issues I had with bup: increasing
> time required to perform the incremental backup on large dataset with
> only few modifications and more importantly the impossibility to prune
> older backups. Also borgbackup natively supports encryption (AES256)
> and authentication (HMAC-SHA256).
> 
> For offline long term backups I also used to work with hashdeep to
> perform and store a hash of all the files and recently started playing
> with FIM https://evrignaud.github.io/fim/ which is similar but with a
> git backend for storing history. Don't get fooled by fim being a java
> application. It easily outperformed hashdeep on large datasets.
> 
> Alphazo


  reply	other threads:[~2016-01-07 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 17:00 Purposely using btrfs RAID1 in degraded mode ? Alphazo
2016-01-04 17:41 ` Chris Murphy
2016-01-06 12:30   ` Alphazo
2016-01-09 10:08   ` Duncan
2016-01-11 22:17     ` Alphazo
2016-01-05 16:34 ` Psalle
2016-01-06 12:34   ` Alphazo
2016-01-07 12:57     ` Psalle
2016-01-07 13:09       ` Alphazo
2016-01-07 17:34         ` Sree Harsha Totakura [this message]
2016-01-11 14:25         ` Psalle

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=568EA19F.4040804@totakura.in \
    --to=sreeharsha@totakura.in \
    --cc=alphazo@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=psalleetsile@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.