Date: Sat, 31 Mar 2001 16:35:30 +0200 From: "Leif Neland" <leifn@neland.dk> To: "ryanb" <ryanb@goddamnbastard.org> Cc: <freebsd-isp@FreeBSD.ORG> Subject: Re: Mirrorred webservers: Updating, logging. Message-ID: <01d501c0ba1f$23cc06a0$6405a8c0@neland.dk> References: <00e201c09c62$fbd45aa0$0e00a8c0@neland.dk> <20010329101658.A87734@bjorn.goddamnbastard.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "ryanb" <ryanb@goddamnbastard.org> To: "Leif Neland" <leif@neland.dk> Cc: <freebsd-isp@FreeBSD.ORG> Sent: Thursday, March 29, 2001 6:16 PM Subject: Re: Mirrorred webservers: Updating, logging. > On Thu, Feb 22, 2001 at 01:04:10AM +0100, Leif Neland wrote: > > We're thinking about mirroring our webservers for redundancy. > > > > There exist different solutions, however, I have not seen any mentioning on how to update the sites; the customers shouldn't have to update two sites; it should work transparently. > > Would there be an option to use an NFS server to house all the content > and logs, thus leaving a common thread for any amount of machines you'd > like to slave from a single set of data? A user could edit/upload to > their space housed on a file server with changes effective immediately > on _all_ client machines. > That still leaves that NFS-server as the single point of failure. So that is no option. I discovered some smart guy had set our secondary nameserver to have its files nfs-mounted from the primary. So much for redundancy... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01d501c0ba1f$23cc06a0$6405a8c0>