From: Gebhardt Thomas (gebhardt_at_hrz.uni-marburg.de)
Date: Thu 04 Mar 2004 - 08:59:25 GMT
On Wednesday 03 March 2004 16:51, loic d'Anterroches wrote:
> Do I am wrong or thanks to the vserver approach I don't need to setup an
> ip takeover? Or formulated another way: heartbeat is only used to start
> the vserver on BB if BA goes down, drbd taking care of the synchro of the
We are running this type of setup here but don't yet have any experience
with "real" hardware failures but only with test situations.
Yes, you are right: heartbeat doesn't need to manage the ip takeover,
vserver does. We emit an unsolitcited arp reply in the vserver pre-start
script in order to inform all hosts in the local subnet about the takeover.
We don't run the rebootmgr because we noticed that its open socket
in the vserver filesystem prevented heartbeat from unmounting the
vserver filesystem and the takeover hangs.
Our heartbeat resources are datadisk, vserver and MailTo, where the
vserver resource script is just a symbolic link to the standard vserver
> Off-topic: If you are using drbd, how are you managing the synchro when
> the master BA comes online again?
Don't know what you want to know here. We have heartbeat configured with
"auto_failback off", so when BA comes up again, the vserver stay on BB
until we interactively force the takeover. So we can have a look at BA
and eventually start drbd on BA if that doesn't happen automagically.
If you want to force a full sync, you have to delete all files in
/var/lib/drbd before reconnecting BA. After drbd has synced the
disk(s) you can do a "/usr/lib/heartbeat/hb_standby foreign" on BB
to force the failback of the vservers.
Vserver mailing list