I had figured this out a while back and forgot to post back to the list. The steps are as follows Create a child script to the virtual ip to check whether mysql is up. Have mysql NOT start on boot. With these two things done. When the vip fails over, it will not fail back because mysql wont be up. Rob Gil Linux Systems Administrator American Home Mortgage ________________________________ From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Bjorn Oglefjorn Sent: Thursday, July 26, 2007 3:18 PM To: linux clustering Subject: Re: MySQL Failover / Failback I found that a 'nofailback' option was added for the <failoverdomains> section of the conf. I can't find any reference to 'nofailback' in any RHCS doc I can find. I'm guessing it should look like this: <failoverdomain name="test_failover_domain" ordered="1" restricted="1" nofailback="1"> ... </failoverdomain> Can someone confirm? I will attempt to confirm this myself and will report back when I know for sure. --BO On 7/26/07, Bjorn Oglefjorn <sys.mailing@xxxxxxxxx> wrote: I'd love to know how to do this as well. Anyone? --BO On 6/1/07, Robert Gil <Robert.Gil@xxxxxxxxxxxxxx <mailto:Robert.Gil@xxxxxxxxxxxxxx> > wrote: 1) Node 1 (master) dies -How do we enable "sticky" failover so that it does not then fail back to Node 1 -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
