Guy Coates wrote:
> Jan Kalcic wrote:
>   
>> Hi People,
>>
>> I'm going to set up a ha cluster  for  apache and  mysql but reading the
>> documentation some doubts came in my mind as I'm not so export in this
>> kind of cluster. It's a two nodes active/passive cluster for a website.
>> A part of the local filesystem (website docs) has to be shared and
>> always in sync. For this purpose I am going to use drbd which as far as
>> I understood it allows me to shared local data between nodes. These two
>> nodes are also attached to a SAN where the mysql database will run on.
>> Here are the doubts. Should it be easier using the SAN only instead of
>> drbd?
>>     
>
> If you have SAN storage, then you do not need to use drbd for either the web 
> or
> the mysql filesystem.
>
> A suggested configuration would be:
>
> One SAN volume for the apache content.
> One SAN volume for the mysql database.
>
> The reason for having two volumes is that it will allow you to config 
> heartbeat
> to run the apache+apache filesystem on one node, and the mysql server + mysql
> filesystem on the other, so you can spread the load.
>
> (There is no technical reason why you can't run drbd on top of SAN volumes, 
> but
> it is another layer of un-needed complexity waiting to go wrong. The simplest
> config you can get away with is going to be the most reliable.)
>
> Cheers,
>
> Guy
>
>   
 
Thanks for your useful suggestion.
 
About the resource configurations I have to say it's an interesting
solution but actually I don't have a load balancing need and to be
honest I don't want to make difficult. I thought to create just a
virtual ip interface resource to failover so that the configuration is
as simple as possible. Do you maybe suggest me to create a resource for
apache and one for mysql instead? Can it be done easily or particular
XML and heartbeat skills are needed?

Jan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to