From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 6 19:38:39 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 EE2D9106568D for ; Mon, 6 Oct 2008 19:38:39 +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 9ECC78FC2F for ; Mon, 6 Oct 2008 19:38:38 +0000 (UTC) (envelope-from yurtesen@ispro.net) Received: (qmail 85327 invoked by uid 399); 6 Oct 2008 19:38:52 -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; 6 Oct 2008 19:38:52 -0000 X-Originating-IP: 130.232.138.155 Message-ID: <48EA6939.6090405@ispro.net> Date: Mon, 06 Oct 2008 22:38:33 +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> <001AD718-D25B-421B-8B0F-CE71FA5A7CF0@gid.co.uk> <48EA21AE.80607@ispro.net> <5f67a8c40810060852k4c51c8far511891c4b135a1e2@mail.gmail.com> In-Reply-To: <5f67a8c40810060852k4c51c8far511891c4b135a1e2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 06 Oct 2008 19:52:17 +0000 Cc: 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: Mon, 06 Oct 2008 19:38:40 -0000 Zaphod Beeblebrox wrote: > On Mon, Oct 6, 2008 at 10:33 AM, Evren Yurtesen > wrote: > > [regarding r1soft.com , ...] > > > I am not saying it is impossible. They just need somebody to put > them to right track I guess. I personally cant do that. It would be > nice if somebody who has knowledge in this area contacts r1soft. At > the very least r1soft seems to be willing to communicate on this issue. > > Continuous backups as well as bare-metal-restore seem to be a key > feature for many hosters. FreeBSD is loosing users because of this > issue. > > > Actually, having looked at the site, the hammer filesystem and it's > replication strategy seem to be the most applicable technology (but then > you wouldn't even need these guys --- you'd be doing it yourself). Like > anything, though, live applications will require special treatment. > Keeping a live filesystem replicated does in no way guarentee that your > database (for instance) will be sane at any particular moment. It > sounds like these guys have made allowances for MySQL (they specifically > mention it), but this won't help the PostgreSQL users, etc. I think you didnt get the point here. Replication or mirroring != backup. You cant return back to how things were 1 hour ago. Also they support postgresql as well (while its usage is way smaller than mysql) http://www.r1soft.com/CDP_db_postgreSQL.html In any case, the product guarantees that it can return your databases to any point in the time. Do you see what you are missing? :) > I've spent a lot of time thinking about redundancy and I've come to one > inescapable conclusion: That the further up the stack you design for > redundancy, the cheaper and easier it becomes. Most databases have > replication strategies of one type or another that don't require exotic > hosting solutions to work. The idea/problem is not redundancy here, it is data protection. Thanks, Evren