From owner-freebsd-cluster@FreeBSD.ORG  Wed Sep 29 22:00:58 2004
Return-Path: <owner-freebsd-cluster@FreeBSD.ORG>
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 EE27116A4CF
	for <freebsd-cluster@freebsd.org>;
	Wed, 29 Sep 2004 22:00:58 +0000 (GMT)
Received: from watcher.puryear-it.com (ip-66-186-248-99.static.eatel.net
	[66.186.248.99])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8BDBB43D5C
	for <freebsd-cluster@freebsd.org>;
	Wed, 29 Sep 2004 22:00:58 +0000 (GMT)
	(envelope-from dustin@puryear-it.com)
Received: from localhost (unknown [127.0.0.1])
	by watcher.puryear-it.com (Postfix) with ESMTP id BBF4034D2F;
	Wed, 29 Sep 2004 16:57:52 -0500 (CDT)
Received: from watcher.puryear-it.com ([127.0.0.1])
 by localhost (watcher.puryear-it.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 50145-10; Wed, 29 Sep 2004 16:57:51 -0500 (CDT)
Received: from THEBOX (localhost [127.0.0.1])
	by watcher.puryear-it.com (Postfix) with SMTP id B24EC34D1E;
	Wed, 29 Sep 2004 16:57:50 -0500 (CDT)
Message-ID: <009d01c4a66f$c6de3ad0$0200a8c0@THEBOX>
From: "Dustin Puryear" <dustin@puryear-it.com>
To: "xyberpix" <xyberpix@xyberpix.com>
References: <1096488485.2760.29.camel@syn>
Date: Wed, 29 Sep 2004 17:00:00 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Virus-Scanned: by amavisd-new
cc: freebsd-cluster@freebsd.org
Subject: Re: Cluster help
X-BeenThere: freebsd-cluster@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Clustering FreeBSD <freebsd-cluster.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-cluster>,
	<mailto:freebsd-cluster-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-cluster>
List-Post: <mailto:freebsd-cluster@freebsd.org>
List-Help: <mailto:freebsd-cluster-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-cluster>,
	<mailto:freebsd-cluster-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Sep 2004 22:00:59 -0000

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