| Re: DRBD+Heartbeat clustering question! [message #30055 is a reply to message #30053] |
Wed, 07 May 2008 10:32   |
dim
Messages: 344
Registered: August 2005
|
Senior Member |
|
|
| zenny wrote on Wed, 07 May 2008 06:04 |
Dim:
1) However, as you advised to have per-Container drdb device instead of GFS, do I need to follow the instructions without formating the /vz volume and then make it a DRBD + ext3 volume later as explained in http://wiki.openvz.org/HA_cluster_with_DRBD_and_Heartbeat ? I meant to install cluster manager in HN node?
|
I didn't advise, I just presented available choices. DRBD is not ideal solution as well, you know. Yes, you need to follow instructions and install cluster manager in HN. But its configuration should differ - each Container should be a resource, not vz service itself.
| Quote: |
2) And then again do I have to install the cluster manager in the containers also to achieve what I thought in the first post? Please elaborate.
|
No, this doesn't help. The problem that in case of failure you need to mount Container's private on failover node in order to start Container, while cluster manager inside it can't do this.
| Quote: |
3) I am yet to figure out two ethernet cards in each node in the above wikipage setup? Is that for the crossover cables to backup data or is it as a failover ethernet card? Just simply wondering!
|
I think it is for performance mostly. DRBD is network replication and its health depends on transfer rate greatly.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
