[DRBD-user] Missing link

[Steven]

Lars Ellenberg wrote:
> On Mon, Aug 27, 2007 at 09:09:54AM +0300, Michael Tewner wrote:
>   
>> Perhaps you're not using the correct hostnames in the Heartbeat and
>> drbd configuration files. These programs are both quite picky over
>> nodenames -
>> drbd needs the uname -n (I think) as nodename.
>> I don't remember what Heartbeat needs - proably the same.
>>
>>
>> On 8/24/07, Steven <drbd at savetimehosting.com> wrote:
>>     
>>> Hi,
>>>
>>> I RTFM many times and googled most uncovered issues BUT there must be
>>> some missing vital link in it.
>>>
>>> 1. The drdb init script loads drbd module and does a bit more BUT it
>>> doesn't decide about its role (primary or secondary); that sounds ok as
>>> it should be heartbeat's task (and I assume that it will issue the right
>>> commands to drbd) so my question is: what config file is the one
>>> responsible for bringing the proper ip address up on the secondary node?
>>>
>>> Logically it should be the /etc/drbd.conf file as the doc only mention
>>> that one service ip should be listed in the /etc/ha.d/haresource file:
>>>
>>> joe drbddisk::r0 Filesystem::/dev/drbd0::/var/lib/mysql::ext3 192.168.99.1 mysql
>>>
>>>
>>> My problem is that heartbeat do NOT bring up the ip for it
>>> (192.168.99.2) and cannot sync.
>>> Am I missing something obvious not mentioned in the documentation (the
>>> missing link) ?
>>>
>>>  on node1 {
>>>    device /dev/drbd0;
>>>    disk /dev/sda1;
>>>    address 192.168.99.1:7788; #service address brought up by heartbeat (on node1)
>>>    meta-disk /dev/sdb1[0];
>>>  }
>>>  on node2 {
>>>    device /dev/drbd0;
>>>    disk /dev/sda1;
>>>    address 192.168.99.2:7788; #service address THAT SHOULD BE BUT IS NOT brought up by heartbeat (on node2)
>>>       
>
> drbd replicates over tcp.
> it needs the ip to be there.
> always.
>
> you do not replicate over some "service" adress, normally.
> you replicate over some static ip on a dedicated replication link.
>   
Thanks for your reply.

So in other words, the ips in the drbd.conf files on both hosts are 
static ips and unrelated to what heartbeat calls service addresses (the 
ones that heartbeat brings up or down based on state). So this ensure 
drdb is fonctionning no matter what and if the main host goes down, then 
hearbeat will properlly bring up the service ip on the secondary hosts 
and mount filesystems which allows clients to access the drbd device on 
the the surviving host.

Thank you Lars.

-- 
Virtual Space International Inc. 
Steven Dugway USA 206-734-HOST Canada 514-939-HOST (4678) ext 5
Skype:stevenvsi; savetimehosting.net 911hosting.net goodprivacy.net
Spam is not allowed: AUP http://www.virtualspaceintl.net/acceptable_use.html
--------------------------------------------------------------
Internet Is Here To Stay, Make Sure Your Business Is!
--------------------------------------------------------------