Date: Mon, 6 Jun 2011 12:01:19 +0200 From: Kai Gallasch <gallasch@free.de> To: Charles Sprickman <spork@bway.net> Cc: freebsd-fs@freebsd.org Subject: Re: zfs snapshot management Message-ID: <F648647B-5D46-4CF2-8C32-EEE0618634BF@free.de> In-Reply-To: <alpine.OSX.2.00.1106052232210.1983@hotlap.nat.fasttrackmonkey.com> References: <alpine.OSX.2.00.1106052232210.1983@hotlap.nat.fasttrackmonkey.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 06.06.2011 um 04:32 schrieb Charles Sprickman: > I've been using a few different tools to manage zfs snapshots in = different > scenarios. For local use, I've found that Ralf Engelschall's set of > scripts[1] that tie into the periodic(8) system work fairly well. I = do > not use the amd portion since I am only working with zfs snapshots and = I > don't see a need to actually re-mount the snapshots elsewhere for > recovery. The only limitation I find with this system is that for use = on > a backups host the lack of a monthly or yearly retention period pretty > much rules it out. For local "oops" stuff though, it's great. >=20 > For hosts acting as backups servers, I've been using Snapfilter[2] and > some cobbled together stuff that rsyncs a bunch of hosts and tries to > detect and notify on errors. Snapfilter simply is the zfs snapshot > "sweeper" that periodically deletes snapshots that are outside the = defined > retention period(s). >=20 > Since there seems to be a fair number of serious zfs users here, I was > hoping for some further suggestions for use in either case. Any input = is > welcome... I'm using zetaback(FreeBSD Port: sysutils/zetaback) for some time now. For backup purposes and for a very convenient method to move zfs based = jails from one host to another.. Have a look at https://labs.omniti.com/labs/zetaback Regards, Kai. -- "I'm tryin' to think but nothin happens" - Curly
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F648647B-5D46-4CF2-8C32-EEE0618634BF>