From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-out1.informatik.tu-muenchen.de ([131.159.0.8]:45394 "EHLO mail-out1.informatik.tu-muenchen.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752929AbcAGRe1 (ORCPT ); Thu, 7 Jan 2016 12:34:27 -0500 Subject: Re: Purposely using btrfs RAID1 in degraded mode ? To: Alphazo , Psalle References: <568BF078.8060303@gmail.com> <568E60CF.70004@gmail.com> Cc: Btrfs BTRFS From: Sree Harsha Totakura Message-ID: <568EA19F.4040804@totakura.in> Date: Thu, 7 Jan 2016 18:34:23 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: 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