From owner-freebsd-isp@FreeBSD.ORG Tue May 27 01:34:27 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 082D837B401 for ; Tue, 27 May 2003 01:34:27 -0700 (PDT) Received: from ns3.unixmexico.net (ns3.unixmexico.net [69.10.137.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4541C43FBF for ; Tue, 27 May 2003 01:34:26 -0700 (PDT) (envelope-from nbari@unixmexico.com) Received: (qmail 22305 invoked by uid 85); 27 May 2003 08:34:39 -0000 Received: from nbari@unixmexico.com by ns3.unixmexico.net by uid 82 with qmail-scanner-1.16 (hbedv: 6.19.0.3/6.19.0.13. Clear:. Processed in 0.307393 secs); 27 May 2003 08:34:39 -0000 Received: from ns3.unixmexico.net (HELO mail.unixmexico.com) ([69.10.137.124]) (envelope-sender ) by ns3.unixmexico.net (qmail-ldap-1.03) with SMTP for ; 27 May 2003 08:34:38 -0000 Received: from 148.243.211.187 (SquirrelMail authenticated user nbari@unixmexico.com) by mail.unixmexico.com with HTTP; Tue, 27 May 2003 03:34:39 -0500 (CDT) Message-ID: <2513.148.243.211.187.1054024479.squirrel@mail.unixmexico.com> In-Reply-To: <200305270929.06746.jamie@tridentmicrosystems.co.uk> References: <2217.148.243.211.187.1054021261.squirrel@mail.unixmexico.com> <1054021870.3ed318ee732fb@www.digitalinscription.net> <2404.148.243.211.187.1054023759.squirrel@mail.unixmexico.com> <200305270929.06746.jamie@tridentmicrosystems.co.uk> Date: Tue, 27 May 2003 03:34:39 -0500 (CDT) From: nbari@unixmexico.com To: jamie@tridentmicrosystems.co.uk User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal cc: freebsd-isp@freebsd.org Subject: Re: replicating data over 2 servers X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 08:34:27 -0000 But if the NFS server A comes down, server B will not have access to the data. or can i have to NFS servers (server A and B) sharing the same data? Cheers > On Tuesday 27 May 2003 9:22 am, nbari@unixmexico.com wrote: >> the problem when using rsync in both servers is that if data on server A >> is updated, and data on server B is updated at the same time, there is >> a >> chance to lost data. >> >> If a user writes to a file on server A and then rsyn is executed data >> will >> be lost, and so if a users writees on server B an rsync tryis to fecth >> from server A data will be lost >> >> how about usind coda? >> or another tool for replication txt files? >> >> > > On server A have a partition/directory dedicated to storing the text > files. > Export this via NFS to server B. > > For backup purposes copy them nightly to server B. > > Cheers, > > Jamie > >