From owner-freebsd-isp Sat May 15 18:11:10 1999 Delivered-To: freebsd-isp@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (Postfix) with ESMTP id 4CAC514FFA for ; Sat, 15 May 1999 18:11:01 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id LAA17687; Sun, 16 May 1999 11:10:45 +1000 (EST) Date: Sun, 16 May 1999 11:10:44 +1000 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Graeme Tait Cc: freebsd-isp@FreeBSD.ORG, info@boatbooks.com Subject: Re: Redundant servers In-Reply-To: <373DD794.15EF@echidna.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How about: http://www.coyotepoint.com/freequalizer.shtml On Sat, 15 May 1999, Graeme Tait wrote: > I operate a colocated server (busy WWW, plus primary DNS and a small > amount of mail) for some clients, and we have been thinking about how to > assure (almost) uninterrupted service in the event of server failure. The > problem is that if physical access is required (e.g., because of hardware > failure), we may at times have difficulty achieving an acceptable repair > time. There is also the issue of minimizing downtime during major > upgrades. Since this machine takes online orders, downtime is directly > translatable into dollars of income lost. > > The existing machine is a plain PII-400 with 512MB RAM and 18GB total > non-RAID SCSI disk, and has been perfectly reliable to date. We could > purchase a fancy "server-grade" machine with RAID, redundant power > supplies, etc., but the fact is that there are still things that could > fail, and we'd still have to go down for certain upgrades. Also, such a > machine would be so expensive that having a spare would be out of the > question at present. > > For less total cost, we can commit a machine identical to the existing > server as a hot-standby, installed in the colo. So my first question is > does anyone have opinions on this or alternative strategies for > maximizing uptime, given that physical access to the server may be > severely restricted? > > > The second issue is how to actually run a hot standby, and effect a > switch on failure of the primary. > > I would want the spare machine on the network, since it could be used for > offloading some background tasks from the live machine, and also for > backing up some critical data. > > My thought was to assign the spare a separate primary IP address, and > have only that address active under normal circumstances. If it became > necessary to switch over from the live server, we would somehow take the > live server off the network (by software, remote power-down or physical > disconnection), and then run a script on the spare to ifconfig the 50 or > so IP alias addresses that the operational server answers to for DNS, > mail and WWW traffic. Maybe this could be automated based on monitoring > the primary machine. > > The other issue is how to make sure the spare machine is basically a > mirror of the primary machine. > > > -- > Graeme Tait - Echidna > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message