[CentOS] Xen, GFS, GNBD and DRBD?

Thu Jan 3 12:50:17 UTC 2008
Ross S. W. Walker <rwalker at medallion.com>

You can fail-over using iSCSI multi-pathing. Have the initiator log in to both targets and then setup dm-multipath to do fail-over. On the target side you could use drbd with multi primaries and there you have it, redundant storage with easy fail-over.

-Ross


-----Original Message-----
From: centos-bounces at centos.org <centos-bounces at centos.org>
To: CentOS mailing list <centos at centos.org>
Sent: Wed Jan 02 20:15:58 2008
Subject: Re: [CentOS] Xen, GFS, GNBD and DRBD?

On 03/01/2008, at 9:55 AM, Ross S. W. Walker wrote:

>
> Take a look at iSCSI for the storage servers. iSCSI Enterprise  
> Target is what I use here and it works well for us.
>
> You don't really need shared filesystems if you are doing direct  
> block io to LVs or raw partitions as the Xen migration will handle  
> the hand-off, but you will if you are using flat files, because of  
> this I recommend using LVs or raw partitions as clustered  
> filesystems will put a serious overhead on the Xen guest io.
>
> -Ross

Ross,

I can use DRBD to mirror data between the two storage servers and  
iSCSI to export the block devices, but how will iSCSI cope with  
failure of one storage server?

Can I use heartbeat and CRM to failover the host IP and iSCSI target  
to the other storage server?

Regards,
Tom
_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20080103/a8fd70be/attachment-0005.html>