From: Simon Kirby <sim@hostway.ca>
To: "K. Richard Pixley" <rich@noir.com>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
linux-btrfs@vger.kernel.org,
Fred van Zwieten <fvzwieten@gmail.com>
Subject: Re: remote mirroring in the works?
Date: Mon, 30 Aug 2010 23:30:31 -0700 [thread overview]
Message-ID: <20100831063031.GE29552@hostway.ca> (raw)
In-Reply-To: <4C7BF51B.2070201@noir.com>
On Mon, Aug 30, 2010 at 11:14:51AM -0700, K. Richard Pixley wrote:
> On 20100830 10:59, Roy Sigurd Karlsbakk wrote:
>>> I think drbd does precisely what you want.
>>>
>>> It's not useful for fault tolerance, nor for load balancing, but it
>>> will
>>> produce a remote block copy that can be used as a sort of "hot
>>> backup".
>> drbd with heartbeat/pacemaker can provide fault tolerance...
> I think that's a matter of semantics.
>
> Once you've failed over from the primary system to the secondary,
> changes to your block device are terminal. It's not easy to produce a
> system which can manage those changes and "heal" in the sense of
> allowing the primary system to return to service. In effect, returning
> the primary system to service requires taking both systems down and
> copying the block device from the secondary back to the first.
This is totally incorrect. DRBD replicates in both directions quite
well, in fact. I've been using it on about 60 machines for many years,
and I have never had to do what you mention.
What it does not help with is avoiding corruption that occurs above the
block layer; eg, if your file system or your database on top of it barfs,
there is no other "good copy". fsck or repair is still required in these
cases. It is just like local RAID 1 in this respect -- you still need a
backup and/or copy at the file level, which is closer to what is needed
here.
Simon-
next prev parent reply other threads:[~2010-08-31 6:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinmSdHwXXq3s64sM39GjacafgwgTjPadZGHuway@mail.gmail.com>
2010-08-30 17:07 ` remote mirroring in the works? Fred van Zwieten
2010-08-30 17:21 ` Bryan Whitehead
2010-08-30 17:33 ` Roy Sigurd Karlsbakk
2010-08-30 17:55 ` K. Richard Pixley
2010-08-30 17:59 ` Roy Sigurd Karlsbakk
2010-08-30 18:14 ` K. Richard Pixley
2010-08-31 6:30 ` Simon Kirby [this message]
2010-08-31 18:44 ` Fred van Zwieten
2010-09-06 21:50 ` David Nicol
2010-09-07 0:04 ` K. Richard Pixley
2010-08-30 21:15 ` Fred van Zwieten
2010-08-30 21:23 ` Freddie Cash
2010-08-30 22:56 ` K. Richard Pixley
2010-08-31 5:07 ` Fred van Zwieten
2010-08-31 6:38 ` Simon Kirby
2010-08-31 18:29 ` Goffredo Baroncelli
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=20100831063031.GE29552@hostway.ca \
--to=sim@hostway.ca \
--cc=fvzwieten@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rich@noir.com \
--cc=roy@karlsbakk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).