From owner-freebsd-stable@FreeBSD.ORG Tue Nov 4 06:06:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 722DB1065674 for ; Tue, 4 Nov 2008 06:06:43 +0000 (UTC) (envelope-from numardbsd@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.freebsd.org (Postfix) with ESMTP id 38BE78FC13 for ; Tue, 4 Nov 2008 06:06:43 +0000 (UTC) (envelope-from numardbsd@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so2968157wfg.7 for ; Mon, 03 Nov 2008 22:06:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:in-reply-to:references:x-mailer:face:mime-version :content-type:content-transfer-encoding; bh=UsUiPo+p8xo9UJsYntbNAbG91UsGO33D9J/0K3E7r8Q=; b=O1W45vjQb9hrEPY55VdJKwDmwruxQGlm9Z/nBHDpsZOhF9vVtlj+JD7YjfRi2gB8Al Y9y2lURAYt0um9Ke4CjN9YiDF8RB8PYYT8pqznWMF2sGbGCubSn76rmevUqKAcWFyotI FcMH2ZBdElZDDkEHxyP0qQvKHJjIw3JhEgxqw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :face:mime-version:content-type:content-transfer-encoding; b=b7aze74vTUwXdW0QcuHw+D2w3dNzGFQ5DseoomGxHUranVSSoo3xhxrECuAVabwTUo aJihPbEQvbzXssZwwgifjP+ajQbkYXl/YxhEGiebg0X7MS+gYj0pRwO9FfKC7DTKSbln yl8v9VzMMwkxUDoXGF2Cb2fBeT5gE4TbjQ1Eo= Received: by 10.142.241.10 with SMTP id o10mr552668wfh.222.1225777356474; Mon, 03 Nov 2008 21:42:36 -0800 (PST) Received: from ayiin (203-166-246-80.dyn.iinet.net.au [203.166.246.80]) by mx.google.com with ESMTPS id 22sm17191026wfg.13.2008.11.03.21.42.34 (version=SSLv3 cipher=RC4-MD5); Mon, 03 Nov 2008 21:42:35 -0800 (PST) Date: Tue, 4 Nov 2008 16:42:30 +1100 From: Norberto Meijome To: freebsd-stable@freebsd.org Message-ID: <20081104164230.013e9887@ayiin> In-Reply-To: <490F6EBF.5000102@minibofh.org> References: <490F6EBF.5000102@minibofh.org> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX+/v7++v6YOTrq8PCcuIX989UvOSj++v0BNCbpAAAAB3RJTUUHsQwfFzs7RBhzUQAAAhJJREFUOI1dU8GOqzAMNKIoV1bvwD1i0ysqrHplIdBrVSX7ATSbd03VVvn9tQNtQy0hjAdn7LED4AAcPtWm9RV+MPSfxhBLx9ajd6X/ngB6/mTwnRSZua7i7Ca+0ctZKo4Qmz+JY13X6I3nFZBxIYW1PbgfQ5RP8g0XlltEWGf3cV03joYpRnFbvYDKbXjZlXyyhEZA4lI+cN3NaVXE4VKjSwTExO10eTEkkJVqIAD5z0nUBQJluQDRSQjcrBiHAJxZlAH5CUMBMC7OcJ4LMQNnxhZ1HYPscMc6J4UlWRMNwzOpCcAHKSICd1EDn83abdREIbXsHkD1OinP1aCUCOEVRaa1lMcvywUWdYgk13JQUpYNKmvXQ8Kw5ML9YI5h8SakctBc7E/IYuLhYd/zZIk+1gM1vNweQBvHE0j+oYah3sMqAytQYlZk6+ANaaawJdu3OFzYGMZ3iGpa3qMlq9ZH0VZTgrCtw/ngdYkEIIpSbP1bWQAdFdX9vocBdkH2qVjVmuMu3gI5rjs814EUdrCZgWlPaxZZ3RiLFUtr+ud0PXwp2dnQSNXgePt6AZpBj6UMJ7VQkzN4utVeaSW1Dhn/kblGrKeMvNGnzwX4zuEDarYz1KdPtR60Gul0Gued+515SJXhCsl+Tx/3kY/UDvicPll9mfu50t3tvQ/thZpJYgeuwdSKNJ6tCD98MCgoxLDaPxbwqqwPWaWiAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Replication system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2008 06:06:43 -0000 On Mon, 03 Nov 2008 22:35:59 +0100 Jordi Espasa Clofent wrote: > Hi all, Hola Jordi, > I have to build a clustered website with FreeBSD 7.x as SO and Apache > 2.x as httpd. As load-balancing solution I'll use HAProxy (or maybe a > OpenBSD relayd, I'm not sure). you may want to look into carp as well if you don't want to have a separate layer of load balancers. > Because of several technical (and especially non-technical) reasons, I > haven't the possibility to mount a shared storage layer (NFS, SAN...) so > I have to share the local data among the different httpd servers. > > At first approach I've thought in rsync+cron, but > > __anyone knows another replication-data solution in the described scenario? rsync / rsyncd is simple and works. But it really depends on how often you'll be publishing to your site, how big are the change sets ( consider publishing to a separate directory via rsync and then doing an atomic rename/move if the change set is too big.) we used to publish from AU to NL to dir1 in server1 , then ssh to server1 and rsync to server2-n in parallel - all from a script of course. That way, the slow link ( AU <-> NL) never got in the way of the publish. B _________________________ {Beto|Norberto|Numard} Meijome He could be a poster child for retroactive birth control. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.