I'm also in strong interest about hearbeat over SAN, because there is not gabdisk support since version 5.
i like to describe why an alternate Hearbeat way is so importend:
if you think about a backup datacenter ( only as a Datacenter without employes ) and one Clusternode should stand in that datacenter.
You plan your cluster with two heartbeat IF over seperate Lines to the backup datacenter.
So far ... everything perfect.
You decide to use both clusternodes for applications / or Databases, just let both nodes working...
And you use I/O Fencing just to take care against split brain... ( i guess that config looks fair ).
But what happens when a big networkfailure stops the whole transfer to ur backup datacenter ????
One of ur cluster nodes crashes ... maybe that one that is in ur primary Datacenter and all services falls to the backup datacenter.
... ok u run into a big problem .. because u have no network to the backup datacenter,, so how u can transfer the services to ur primary datacenter ??..
Before Version 5 we use the on to the gabdisk to prepare us against networkfailure and that works perfect.
Why !!!!!! is that feature not more available ???????..
It 's not more possible to build up HA Solutions in that limited way,, so im also searching an alternate way for
Heartbeating between the cluster nodes ,, or i have to search an other cluster SW.
( i dont like... )
Is there really no way to get back the gabdisk feature ??
So an alternate way will be ( maybe ) IP over FC ,, just to use other lines... not perfect but better then nothing..
Is there a roadmap to make this as a supported way ??..
Need ur help ....
Thanks a lot!