From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 12:01:15 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 544D016A4CF for ; Fri, 22 Apr 2005 12:01:15 +0000 (GMT) Received: from parrot.aev.net (host29-15.pool8174.interbusiness.it [81.74.15.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id F336943D1D for ; Fri, 22 Apr 2005 12:01:13 +0000 (GMT) (envelope-from ml@netfence.it) Received: from soth.ventu (adsl-205-23.37-151.net24.it [151.37.23.205]) (authenticated bits=128) by parrot.aev.net (8.13.4/8.13.4) with ESMTP id j3MC4Dqr072713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 22 Apr 2005 14:04:19 +0200 (CEST) (envelope-from ml@netfence.it) Received: from netfence.it (xanatar.ventu [10.1.2.6]) (authenticated bits=0) by soth.ventu (8.13.3/8.13.1) with ESMTP id j3MC0AtM083066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 22 Apr 2005 14:00:11 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <4268F5BF.7030302@netfence.it> Date: Fri, 22 Apr 2005 15:01:51 +0200 From: Andrea Venturoli User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.6) Gecko/20040117 X-Accept-Language: it,en,fr,de MIME-Version: 1.0 To: BSD , freebsd-questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.51 on 192.168.2.2 Subject: Re: =?iso-8859-1?q?R=E9p_=3A_Cluster_on_freeBSD_5=2E3?= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 12:01:15 -0000 BSD wrote: > - DNS (BIND) This is quite easy: just set up one of your server as master, the other as slave. You can configure your clients to use both, and, as an additional benefit, use VRRP or CARP to provide faster recover in case of failure. > - LDAP Client Hm, do you mean server? In that case OpenLDAP provides replication and works quite fine if your LDAP is read-only. If it is read-write, then modifications will temporarily be disallowed when the master fails. > - NTPD You should have no problem. > - WebMin Sorry, I don't know this software. > - Mail (Postfix) > - POP3 > - POP3s This is getting harder: you can have to different server for outgoing mail (using VRRP or CARP). If these are the MX for a domain, you can list them both in the DNS. Then you have two choices: _ one forwards mail to the other, from which the clients download via POP3; in case of failure you still receive all messages, but your user won't see them until the master is fixed; _ both are POP3 server from which clients download; when one fails, the other keeps working fine, but the messages which are stored on the former won't be downloadable until it's fixed. I'm not aware of any application-level solution to this, so I guess further development would probably require a read-write filesystem failover solution, which I never tried. Others have suggested heathbeat, but it's something I have yet to study. > - Mailing List (Sympa) I guess it might be part of the above. Wouldn't it? bye av.