From owner-freebsd-questions@FreeBSD.ORG Mon May 31 11:09:36 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 60F6916A4CE for ; Mon, 31 May 2004 11:09:36 -0700 (PDT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1D7843D2D for ; Mon, 31 May 2004 11:09:35 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.84.3]) by out002.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040531180849.GYRG9273.out002.verizon.net@[192.168.1.3]>; Mon, 31 May 2004 13:08:49 -0500 Message-ID: <40BB74B1.50009@mac.com> Date: Mon, 31 May 2004 14:08:49 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: adp References: <020501c44619$d44e6250$6501a8c0@yourqqh4336axf> <20040531070407.GA50113@happy-idiot-talk.infracaninophile.co.uk> <01a801c44735$9b5eb310$6501a8c0@yourqqh4336axf> In-Reply-To: <01a801c44735$9b5eb310$6501a8c0@yourqqh4336axf> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [68.161.84.3] at Mon, 31 May 2004 13:08:49 -0500 cc: questions@freebsd.org Subject: Re: NFS server fail-over - how do you do it? 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: Mon, 31 May 2004 18:09:36 -0000 adp wrote: > We can live with the chance that a file write might fail as long as we can > switch over to another NFS server if the primary fails. Sorry, NFS simply won't work with the model of operation you've described. There is no way to do fallback to a secondary NFS server if the primary goes down when using read/write shares, nor does there exist any way to push the changes made to a secondary fileserver back to the primary, even if you could convince the clients to fail-over in the first place. Maybe Samba/CIFS would come closer to what you want, or else WebDAV over HTTP? -- -Chuck