From: Nix <nix@esperi.org.uk>
To: Roman Mamedov <rm@romanrm.net>
Cc: Wols Lists <antlists@youngman.org.uk>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Encrypted software RAID1 with Debian Stretch
Date: Fri, 15 Sep 2017 12:35:41 +0100 [thread overview]
Message-ID: <87k210p52q.fsf@esperi.org.uk> (raw)
In-Reply-To: <20170914212206.272b1289@natsu> (Roman Mamedov's message of "Thu, 14 Sep 2017 21:22:06 +0500")
On 14 Sep 2017, Roman Mamedov said:
> On Thu, 14 Sep 2017 16:02:31 +0100
> Nix <nix@esperi.org.uk> wrote:
>
>> I would never consider snapshots on the same filesystem to be a backup
>> of anything, except possibly as a defence against 'oh whoops I rm'ed the
>> wrong tree'.
>
> No one proposed that.
Oh I thought that was what people were proposing as the compelling btrfs
advantage.
> The scenario is that the backup server would have its
> rsync destination dir (from multiple other systems) periodically snapshotted,
> providing a historic view of what it contained 1-2-3 months ago. Just like
> "bup" does in userspace, I guess? -- or like rdiff-backup did, which I used
> before. But now we have that directly in filesystem, no need to cling to
> userspace crutches anymore.
I'm fairly sure that can't deduplicate anywhere near as effectively. No
dedup within files; no dedup across trees (very important if you have
duplicated data on multipl systems you are backing up); no dedup
anywhere except in immediate history. That's all rdiff-backup could do,
but the state of the art is better now.
--
NULL && (void)
next prev parent reply other threads:[~2017-09-15 11:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 23:58 Encrypted software RAID1 with Debian Stretch commentsabout
2017-09-01 9:46 ` Wols Lists
2017-09-12 23:30 ` Nix
2017-09-13 1:34 ` Reindl Harald
2017-09-13 13:52 ` Nix
2017-09-13 16:10 ` Wols Lists
2017-09-14 11:08 ` Nix
2017-09-14 12:01 ` Wols Lists
2017-09-14 13:08 ` Nix
2017-09-14 13:39 ` Roman Mamedov
2017-09-14 15:02 ` Nix
2017-09-14 16:22 ` Roman Mamedov
2017-09-15 11:35 ` Nix [this message]
2017-09-14 17:01 ` Reindl Harald
2017-09-14 16:56 ` Wols Lists
2017-09-15 11:38 ` Nix
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=87k210p52q.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.net \
/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.