From: Michael Schuerig <michael.lists@schuerig.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup for a raid1
Date: Fri, 14 Mar 2014 09:56:20 +0100 [thread overview]
Message-ID: <1549230.7yEi5AM4H9@fuchsia> (raw)
In-Reply-To: <pan$60e7c$45de97e1$2fb9daeb$288befdc@cox.net>
On Friday 14 March 2014 06:42:27 Duncan wrote:
> N-way-mirroring is actually my most hotly anticipated feature for a
> different reason[2], but for you it would work like this:
>
> 1) Setup the 3-way (or 4-way if preferred) mirroring and balance to
> ensured copies of all data on all devices.
>
> 2) Optionally scrub to ensure the integrity of all copies.
>
> 3) Disconnect the backup device(s). (Don't btrfs device delete, this
> would remove the copy. Just disconnect.)
>
> 4) Store the backups.
>
> 5) Periodically get them out and reconnect.
>
> 6) Rebalance to update. (Since the devices remain members of the
> mirror, simply outdated, the balance should only update, not rewrite
> the entire thing.)
>
> 7) Optionally scrub to verify.
>
> 8) Repeat steps 3-7 as necessary.
Judging from your description, N-way mirroring is (going to be) exactly
what I was hoping for.
Michael
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
next prev parent reply other threads:[~2014-03-14 8:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 19:12 Incremental backup for a raid1 Michael Schuerig
2014-03-13 19:28 ` Hugo Mills
2014-03-13 19:48 ` Andrew Skretvedt
2014-03-13 21:09 ` Brendan Hide
2014-03-13 21:14 ` Michael Schuerig
2014-03-13 22:04 ` Chris Murphy
2014-03-13 23:03 ` Michael Schuerig
2014-03-14 0:29 ` George Mitchell
2014-03-14 1:14 ` Lists
2014-03-14 3:37 ` Chris Murphy
2014-03-15 11:35 ` Michael Schuerig
2014-03-15 11:53 ` Hugo Mills
2014-03-15 16:01 ` George Mitchell
2014-03-14 6:42 ` Duncan
2014-03-14 8:56 ` Michael Schuerig [this message]
2014-03-14 11:24 ` Duncan
2014-03-14 13:46 ` George Mitchell
2014-03-14 14:36 ` Duncan
2014-03-14 14:44 ` Austin S Hemmelgarn
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=1549230.7yEi5AM4H9@fuchsia \
--to=michael.lists@schuerig.de \
--cc=linux-btrfs@vger.kernel.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