Date: Mon, 31 May 2004 14:08:49 -0400 From: Chuck Swiger <cswiger@mac.com> To: adp <dap99@i-55.com> Cc: questions@freebsd.org Subject: Re: NFS server fail-over - how do you do it? Message-ID: <40BB74B1.50009@mac.com> In-Reply-To: <01a801c44735$9b5eb310$6501a8c0@yourqqh4336axf> References: <020501c44619$d44e6250$6501a8c0@yourqqh4336axf> <20040531070407.GA50113@happy-idiot-talk.infracaninophile.co.uk> <01a801c44735$9b5eb310$6501a8c0@yourqqh4336axf>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40BB74B1.50009>