From owner-freebsd-fs@FreeBSD.ORG Tue Jun 7 09:29:15 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 026461065673 for ; Tue, 7 Jun 2011 09:29:15 +0000 (UTC) (envelope-from bartosz.stec@it4pro.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id A8DE78FC16 for ; Tue, 7 Jun 2011 09:29:14 +0000 (UTC) Received: from mb01.admin.lan.kkip.pl ([10.66.3.0]) by mainframe.kkip.pl with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QTsav-0007PU-IF for freebsd-fs@freebsd.org; Tue, 07 Jun 2011 11:29:12 +0200 Message-ID: <4DEDEF61.7040008@it4pro.pl> Date: Tue, 07 Jun 2011 11:29:05 +0200 From: Bartosz Stec Organization: IT4Pro User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: bartosz.stec@it4pro.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.1 X-Spam-Score-Int: -80 X-Exim-Version: 4.76 (build at 12-May-2011 10:41:54) X-Date: 2011-06-07 11:29:12 X-Connected-IP: 10.66.3.0:3761 X-Message-Linecount: 56 X-Body-Linecount: 42 X-Message-Size: 2275 X-Body-Size: 1613 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Subject: Re: zfs snapshot management X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 09:29:15 -0000 W dniu 2011-06-06 04:32, Charles Sprickman pisze: > Hello all, > > 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. > > 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). > > 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... > > Thanks, > > Charles > > [1] - http://people.freebsd.org/~rse/snapshot/ > [2] - http://www.scottlu.com/Content/Snapfilter.html I'm using periodic scripts from here: http://www.neces.com/blog/technology/integrating-freebsd-zfs-and-periodic-snapshots-and-scrubs as simple "set and forget" zfs snapshot management approach. They are included into ports tree too: sysutils/zfs-periodic/ I found them much more convenient than Ralf S. Engelschall's solution. Cheers! -- Bartosz Stec