Date: Wed, 8 Oct 2008 13:19:25 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: freebsd-hackers@freebsd.org, "Zaphod Beeblebrox" <zbeeble@gmail.com>, Volker <volker@vwsoft.com>, "Evren Yurtesen" <yurtesen@ispro.net> Subject: Re: continuous backup solution for FreeBSD Message-ID: <5f67a8c40810081019w79e0bb42i49c4da623b6e08ab@mail.gmail.com> In-Reply-To: <200810081120.m98BK2fV043545@lurza.secnetix.de> References: <86iqs3sdtp.fsf@ds4.des.no> <200810081120.m98BK2fV043545@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 8, 2008 at 7:20 AM, Oliver Fromme <olli@lurza.secnetix.de>wrote= : > Dag-Erling Sm=F8rgrav wrote: > > FWIW, the HAMMER file system _does_ support replication to > remote targets (thus "separate"). Unfortunately they call > this feature "mirroring", which is misleading at best. > It's really rather a replication mechanism, much like the > binlog of MySQL. It can be used for various purposes, > including live mirroring, delayed mirroring, archiving, > backup and point-in-time recovery [thank-you for repeating that, BTW] > However, ZFS does exist on FreeBSD, and I think it wouldn't > be impossible to add similar features to ZFS. Possibly even as a ZFS module? This might be something better addressed a= t the ZFS project level --- but the next question is: does FreeBSD support ZF= S modules? > Another possibility would be to extend gjournal by adding > time stamps to journal transactions and a possibility to > feed the journal to a pipe, socket or whatever. And of > course a client-side implementation that does something > useful with the journal stream. This might even be a good > SoC project. Now this interests me. Firstly, I thought that gjournal might only be responsible for the meta-data (but I'm happy to be wrong on this point). Secondly, is it a) sufficient and b) efficient to attempt to time-travel UF= S with the gjournal log?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40810081019w79e0bb42i49c4da623b6e08ab>