From owner-freebsd-cluster@FreeBSD.ORG Wed Sep 29 22:19:07 2004 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB1FE16A4CE for ; Wed, 29 Sep 2004 22:19:07 +0000 (GMT) Received: from freebsdcluster.org (freebsdcluster.dk [195.184.98.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B4FA43D4C for ; Wed, 29 Sep 2004 22:19:07 +0000 (GMT) (envelope-from lasse@freebsdcluster.org) Received: from localhost (localhost.dk [127.0.0.1]) by freebsdcluster.org (Postfix) with ESMTP id CDD74622A; Thu, 30 Sep 2004 00:20:48 +0200 (CEST) Received: from freebsdcluster.org ([127.0.0.1]) by localhost (freebsdcluster.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36151-03; Thu, 30 Sep 2004 00:20:41 +0200 (CEST) Received: by freebsdcluster.org (Postfix, from userid 65534) id 4DDE56234; Thu, 30 Sep 2004 00:20:41 +0200 (CEST) Received: from host-84-9-26-23.bulldogdsl.com (host-84-9-26-23.bulldogdsl.com [84.9.26.23]) by www.freebsdcluster.org (IMP) with HTTP for ; Thu, 30 Sep 2004 00:20:40 +0200 Message-ID: <1096496440.415b353902146@www.freebsdcluster.org> Date: Thu, 30 Sep 2004 00:20:41 +0200 From: "Lasse L. Johnsen" To: xyberpix References: <1096488485.2760.29.camel@syn> <009d01c4a66f$c6de3ad0$0200a8c0@THEBOX> <1096494446.2760.37.camel@syn> In-Reply-To: <1096494446.2760.37.camel@syn> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 X-Originating-IP: 84.9.26.23 X-Virus-Scanned: by amavisd-new at example.com cc: "FreeBSD-cluster\[List\]" cc: Dustin Puryear Subject: Re: Cluster help X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 22:19:07 -0000 Hello, Have a look at freevrrpd (http://www.freebsd.org/cgi/url.cgi?ports/net/freevrrpd/pkg-descr) it a nice tool for sharing one IP address between two machines. So for instance machine A has IP 10.0.0.2 and machine B has IP 10.0.0.3. If you run vrrpd on them both, you can give machine A the additional IP address 10.0.0.1, machine B will then constantly check that machine A is running. In case it's not, machine B will assume the IP address 10.0.0.1. vrrpd also provide hooks for launching various scripts when a switch happen so you can start up say a postfix instance on machine B to take over the job of machine A. (I'm sure the documentation explains it better than me). Hope you make it work. Br, Lasse Quoting xyberpix : > Hi Dustin, > > Ok, so things are sounding positive already, this is great news! > > As for using a load balancer, not an option, this is for home use, not > work, so the finances are a bit low. :( > As for the using MX records, I could do that, but the only problem is > that I only have 1 external IP addy, so unless someone is willing to > donate a spare one, and set up routing for me for nothing, which I can't > really see happening, this isn't really an option right now. I have > looked into getting more IP addy's from my ISP, but all the effort is > not really worth it at this point, and neither is the price. > You mentioned various tools available for FreeBSD for IP failover, can > you maybe please let me have some names, as this may be a good option > for me. > As for if a server fails over, it would be nice to have access to the > primary servers files, but this isn't really a necessity, as I am sure I > can accomplish this with nightly backups, and then a script to copy > things over to the secondary server, what do you think? > > Thanks again > xyberpix > > > On Wed, 2004-09-29 at 23:00, Dustin Puryear wrote: > > Hi. This is definitely doable. Some options: > > > > 1. Use a front-end load-balancer. This makes your life very easy. > > 2. Use MX records. > > 3. Use various tools available for FreeBSD for IP fail-over. > > > > One of your biggest concerns is going to be storage. If a server fails-over > > do you need to worry about the secondary server having access to the > > primary's files? You didn't provide quite enough detail for me to tell. > > > > --- > > Puryear Information Technology, LLC > > Baton Rouge, LA * 225-706-8414 > > http://www.puryear-it.com > > > > Author of "Best Practices for Managing Linux and UNIX Servers" > > Download your free copy: > > http://www.puryear-it.com/bestpractices_ebook.htm > -- > For Security and Open Source news: > http://xyberpix.demon.co.uk > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.