From owner-freebsd-questions@FreeBSD.ORG Sun Sep 5 01:58:21 2004 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 DDD7A16A4CF for ; Sun, 5 Sep 2004 01:58:21 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9161A43D39 for ; Sun, 5 Sep 2004 01:58:21 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i851wLcp030153; Sat, 4 Sep 2004 20:58:21 -0500 (CDT) (envelope-from dan) Date: Sat, 4 Sep 2004 20:58:20 -0500 From: Dan Nelson To: "Marc G. Fournier" Message-ID: <20040905015820.GA44261@dan.emsphone.com> References: <20040904222712.F812@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040904222712.F812@ganymede.hub.org> X-OS: FreeBSD 5.3-BETA2 X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: File system replication between servers 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: Sun, 05 Sep 2004 01:58:22 -0000 In the last episode (Sep 04), Marc G. Fournier said: > Does anyone know of any software that will run on FreeBSD that would > allow you to keep two servers in sync? All writes to /dir1 on > server1 would go to /dir1 on server2, and all writes to /dir2 on > server2 would go to /dir2 on server1? > > I've thought about rsync, but am trying to get it as close to real > time as I can, and on large file systems, rsync would just get too > far behind, too quickly ... > > I've started to look at Coda6, but so far what I'm reading through > the docs makes it sound like it may not be suitable ... > > What I'm looking for is a hot failover solution using FreeBSD ... if > server1 goes down, server2 can start up and continue working ... when > server1 comes back up again, changes to server2 could be re-sync'd > back to server1, and server1 could once more resume its duties ... How about a shared SCSI drive, filesystems only mounted on the master. When the master fails, the slave fscks the filesystems, mounts them, and becomes the master. Tried and true. You could even use background fsck and get immediate failover. You could even do it without shared storage if you use geom_gate and geom_{mirror,vinum,ccd} to keep two identical disks on each machine in sync. When the master crashes and comes back up as a slave, the mirror code will update its disks. -- Dan Nelson dnelson@allantgroup.com