Date: Sat, 1 Dec 2001 16:49:34 +0100 From: "Leif Neland" <leifn@neland.dk> To: "Patrick O'Reilly" <patrick@mip.co.za>, "Chris Fedde" <chris@fedde.littleton.co.us> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: Load balancing stuff (mainly samba) Message-ID: <00b701c17a7f$ca784740$6d05a8c0@neland.dk> References: <NDBBIMKICMDGDMNOOCAICEFMEAAA.patrick@mip.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Patrick O'Reilly" <patrick@mip.co.za> To: "Chris Fedde" <chris@fedde.littleton.co.us> Cc: <freebsd-questions@FreeBSD.ORG> Sent: Friday, November 30, 2001 8:20 AM Subject: RE: Load balancing stuff (mainly samba) > > Take a look at coda. It uses a scheme of local cacheing and > > replication to present a common file hierarchy over a potentialy > > large number of servers. IIRC samba can share a coda filesystem. > > > > This looks interesting! > > I have been asked to set up a mail server with a hot backup which could > take over should the first server fail. Does anyone have any > "real-world" experience using coda for this type of problem? > > Does coda even fit this problem? It is described as a replicated > network file system. That tells me that data would be kept safe by > replication, but there may still be a single point of failure, namely > the mail server itself which is simply making use of the file system. > > Any comments? > If you use two machines, and having mailservers (smtp and pop3) on both, I think that would work. Either the same machine as hosting the coda, or use two others for that. You could write a script to change the ip of smtp and pop3 to point to the active server using ddns. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00b701c17a7f$ca784740$6d05a8c0>