From owner-freebsd-cluster@FreeBSD.ORG Tue Jun 17 12:18:13 2003 Return-Path: Delivered-To: freebsd-cluster@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08E5837B401 for ; Tue, 17 Jun 2003 12:18:13 -0700 (PDT) Received: from walnut.he.net (walnut.he.net [64.71.137.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9137143F85 for ; Tue, 17 Jun 2003 12:18:12 -0700 (PDT) (envelope-from kmacy@fsmware.com) Received: from localhost (kmacy@localhost) by walnut.he.net (8.8.6p2003-03-31/8.8.2) with ESMTP id MAA10326; Tue, 17 Jun 2003 12:18:14 -0700 Date: Tue, 17 Jun 2003 12:18:14 -0700 (PDT) From: Kip Macy X-Sender: kmacy@walnut.he.net To: Gabriel Ambuehl In-Reply-To: <69186061515.20030617211349@buz.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-cluster@freebsd.org Subject: Re: Re[2]: iSCSI and clustering with FreeBSD X-BeenThere: freebsd-cluster@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Clustering FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 19:18:13 -0000 > > The ASPs usually run their own, DB backed code and thus can count on > the DB to replicate itself, no? Or have gone to the trouble to write their own replication layer. I know of at least on ASP that wrote one on top of MySQL before MySQL provided its own replication support. > Or Akamai have mostly static stuff they can just rsync or so... As a cache you can just refetch the original data. That is the beauty of caching, as data loss is a major concern with file systems. -Kip