From: George Mitchell <george@chinilu.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup for a raid1
Date: Fri, 14 Mar 2014 06:46:19 -0700 [thread overview]
Message-ID: <5323082B.50600@chinilu.com> (raw)
In-Reply-To: <pan$4e795$762009e5$6f734697$16ccd0b0@cox.net>
Actually, an interesting concept would be to have the initial two drive
RAID 1 mirrored by 2 additional drives in 4-way configuration on a
second machine at a remote location on a private high speed network with
both machines up 24/7. In that case, if such a configuration would
work, either machine could be obliterated and the data would survive
fully intact in full duplex mode. It would just need to be remounted
from the backup system and away it goes. Just thinking of interesting
possibilities with n-way mirroring. Oh how I would love to have n-way
mirroring to play with!
On 03/14/2014 04:24 AM, Duncan wrote:
> Michael Schuerig posted on Fri, 14 Mar 2014 09:56:20 +0100 as excerpted:
>
> [Duncan posted...]
>
>>> 3) Disconnect the backup device(s). (Don't btrfs device delete, this
>>> would remove the copy. Just disconnect.)
> Hmm... Looking back at what I wrote...
>
> Presumably either have the filesystem unmounted for the disconnect (and
> ideally, the system off, tho with modern drives in theory that's not an
> issue, but still good if it can be done), or at least remounted read-only.
>
> I had guessed that was implicit, but making it explicit is probably best
> all around, just in case. At least I can rest better with it, having
> made that explicit.
>
next prev parent reply other threads:[~2014-03-14 13:45 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
2014-03-14 11:24 ` Duncan
2014-03-14 13:46 ` George Mitchell [this message]
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=5323082B.50600@chinilu.com \
--to=george@chinilu.com \
--cc=1i5t5.duncan@cox.net \
--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