Re: [Xen-users] easy high availability storage

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

>>> On 2009/11/25 at 20:17, "Fajar A. Nugraha" <fajar@xxxxxxxxx> wrote:
> On Wed, Nov 25, 2009 at 5:01 PM, Peter Braun <xenware@xxxxxxxxx> wrote:
>> Hi,
>>
>> take a look at this document
>>
>> 
> http://communities.vmware.com/servlet/JiveServlet/previewBody/10964-102-2-9835/h
>  
> a_san_how-to.pdf;jsessionid=12BC07515EE5DB61AEFA58BA9251110D
>>
>> Its describing building highly-available SAN iSCSI storage on ubuntu.
> 
> 
> It's great to see a how-to for this kind of setup, but here's two
> comments from me:
> - using GFS2 with fence "manual" is, AFAIK, asking for trouble. One of
> the reasons I chose OCFS2 is that it can work without fencing (at
> least better than GFS), and it can automatically reboot itself when it
> detects "something wrong that can cause inconsistency" .

I use OCFS2, as well, and very much appreciate this feature.  Obviously it gets 
a little annoying when one of the servers reboots itself during a production 
day, but this sure beats filesystem corruption.  Furthermore, if you configure 
Heartbeat correctly (or some other CRM tool), you can have the domUs 
automatically started up on your other nodes.

> - if you're sharing using iscsi target, it might be easier (and also
> much better performance) to simply use LVM-backed LUNs instead of
> file-backed LUNs. Thus you only need clvm.

I use EVMS for both my iSCSI and FC-based storage, simply because it's included 
with SLES10.  Seems they've removed it in SLES11, so my upgrade path is a 
little uncertain :-(.

-Nick



--------
This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users