From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 8 18:01:05 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D68501065689 for ; Wed, 8 Oct 2008 18:01:05 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: from mail.ispro.net (mail.ispro.net [87.251.0.19]) by mx1.freebsd.org (Postfix) with ESMTP id 7BE518FC19 for ; Wed, 8 Oct 2008 18:01:04 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: (qmail 45785 invoked by uid 399); 8 Oct 2008 18:01:19 -0000 Received: from perpetual.yok.utu.fi (HELO ?130.232.138.155?) (yurtesen@ispro.net@130.232.138.155) by mail.ispro.net with ESMTPAM; 8 Oct 2008 18:01:19 -0000 X-Originating-IP: 130.232.138.155 Message-ID: <48ECF564.7000204@ispro.net> Date: Wed, 08 Oct 2008 21:01:08 +0300 From: Evren Yurtesen User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Zaphod Beeblebrox References: <48E9E1BB.6020908@ispro.net> <48EA56BB.6040702@vwsoft.com> <48EA8B3A.3090609@ispro.net> <861vysiv9i.fsf@ds4.des.no> <5f67a8c40810070937r5ba89773ncee407ace25fa0dd@mail.gmail.com> <86iqs3sdtp.fsf@ds4.des.no> <5f67a8c40810081015p2c14e38evbeed0a97242a7c4a@mail.gmail.com> In-Reply-To: <5f67a8c40810081015p2c14e38evbeed0a97242a7c4a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Wed, 08 Oct 2008 18:06:24 +0000 Cc: Volker , =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , hackers@freebsd.org Subject: Re: continuous backup solution for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2008 18:01:05 -0000 Zaphod Beeblebrox wrote: > On Wed, Oct 8, 2008 at 4:14 AM, Dag-Erling Smørgrav > wrote: > > "Zaphod Beeblebrox" > > writes: > > "Dag-Erling Smørgrav" > writes: > > > What really annoys me with this thread is that nobody has provided > > > any information at all that would allow someone to understand what > > > needs to be done and estimate how hard it would be. > > Well... I hinted that a hammer port would be sufficient (although > they > > need to finish their replication design) and I hinted that the hammer > > approach may be graftable to ZFS. Both reasonably large effort-wise > > (but probably within the scope of a single developer with sufficient > > time). > > No... you're so far off the mark it's not even funny, especially when > it's been repeatedly pointed out to you. This is not a file system, > it's a backup system. It's not designed to survive a disk crash or an > accidental file deletion, it's designed to survive a direct missile > strike on your colo center. > > To quote Wikipedia, "CDP is a service that captures changes to data to a > separate storage location" - emphasis on "separate". > > > Wow... thanks for the flame, but there's no reason that the device that > is receiving the hammer replication couldn't be on the other side of the > globe and there's no reason it couldn't be considered a backup. Part of > the advantage of the structure that allows you to efficiently select for > new changes allows you to do the same kind of *backup* as they claim. > Wouldnt that device need to keep the whole filesystem? Like if you have 10 machines with 10x 1GB drives (lets say each used about 250gb), you will need 10TB disk space in the backup server?