Date: Fri, 18 Feb 2011 17:39:10 -0800 From: Freddie Cash <fjwcash@gmail.com> To: Denny Schierz <linuxmail@4lin.net> Cc: freebsd-cluster@freebsd.org Subject: Re: Build failover ZFS, like HA-Storage from Solaris Message-ID: <AANLkTimi=mJby_g3_xFn-C1XeUdzq31Mt5-oT6ic%2BvgL@mail.gmail.com> In-Reply-To: <BEB41E6D-D44E-4E9B-A176-EE2EBF63B099@4lin.net> References: <1298020090.18890.1684.camel@pcdenny> <AANLkTi=LNUWCpQ4XsLxYPomRsb3GC0oUrZuvKTyGxqTQ@mail.gmail.com> <BEB41E6D-D44E-4E9B-A176-EE2EBF63B099@4lin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 18, 2011 at 3:44 PM, Denny Schierz <linuxmail@4lin.net> wrote:
> Am 18.02.2011 um 21:29 schrieb Freddie Cash:
>
>> You create a separate hast device for each physical harddrive in the
>> system. =C2=A0That "mirrors" the drives between the two servers.
>
> why should I mirror the drives, while both systems are connected to one s=
as storage? Both hosts can see all drives at the same time, via the SAS HBA=
.
Sorry, re-reading your original post I see that I mixed up the layers. :)
To make sure I understand completely, you have:
[ SAN box ] ---- iSCSI ---- [ node 1 using ZFS ]
\-------- [ node 2 using ZFS ]
Correct? And you want to fail-over services from node 1 to node 2?
You don't need HAST in that situation, as the SAN handles making the
storage available to both. My bad.
But you can still use CARP and devd. CARP provides the shared IP so
that other systems won't notice the switch over. And devd provides
the hooks into your custom scripts so that when CARP switches from
node 1 to node 2, you export the pool on node 1, and import the pool
on node 2.
--=20
Freddie Cash
fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimi=mJby_g3_xFn-C1XeUdzq31Mt5-oT6ic%2BvgL>