I am just wondering, why would you like to do it this way?
If you have SAN then by implication you have a storage array on the SAN. This storage array will normally have capability to give you highly available storage through RAID{1,5,6}. Moreover, any decent array will also provide redundancy in case of a failure of one of is controllers. Then standard dual fabric FC SAN configuration will give you multiple paths to the controllers of the array - normally at least 4 paths. What remains to be done on the servers is to configure device mapper multipath to fit your SAN configuration and capabilities of the array. Most modern arrays these days are active-active and support ALUA extensions.
Nothing specifically needs to be done in the cluster software. This works the same way as for a single host.
Are you trying to build a stretched cluster across multiple sites with a SAN array in each?
Regards,
Chris Jankowski
-----Original Message-----
From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of urgrue
Sent: Saturday, 30 April 2011 19:01
To: linux-cluster@xxxxxxxxxx
Subject: How do you HA your storage?
I'm struggling to find the best way to deal with SAN failover.
By this I mean the common scenario where you have SAN-based mirroring.
It's pretty easy with host-based mirroring (md, DRBD, LVM, etc) but how
can you minimize the impact and manual effort to recover from losing a
LUN, and needing to somehow get your system to realize the data is now
on a different LUN (the now-active mirror)?
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
