From owner-freebsd-isp Thu Sep 12 7:22:42 2002 Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B10E37B400 for ; Thu, 12 Sep 2002 07:22:39 -0700 (PDT) Received: from floyd.gnulife.org (floyd.gnulife.org [199.86.41.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D871F43E6E for ; Thu, 12 Sep 2002 07:22:38 -0700 (PDT) (envelope-from jamie@gnulife.org) Received: by floyd.gnulife.org (Postfix, from userid 1000) id 1ECCC432F2; Thu, 12 Sep 2002 10:02:08 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by floyd.gnulife.org (Postfix) with ESMTP id 0FF04432EE for ; Thu, 12 Sep 2002 10:02:08 -0500 (CDT) Date: Thu, 12 Sep 2002 10:02:07 -0500 (CDT) From: Billy Joe Jim Bob To: freebsd-isp@freebsd.org Subject: [OT] Documentation related to redundancy Message-ID: <20020912095141.H12143-100000@floyd.gnulife.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello! I work at an ISP where we run nothing but FreeBSD on our systems. We're interested in setting up a redundant line of servers which will either 1) Start up automatically if one of the primary servers fails, or 2) Secondary servers which will only become active when we designate them to be active, but will constantly be running to mirror the data on their primary counterpart. Anyway, in short, we're interested in redundancy so that we can provide reliable service, but we've never engineered anything like this before. Can anyone point me in the direction of some documentation which covers tips and ideas for building redundancy for a FreeBSD based ISP? Thanks! - Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message