From owner-freebsd-stable@FreeBSD.ORG Sat Mar 2 15:09:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F32BD8B7; Sat, 2 Mar 2013 15:09:48 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 69E4095; Sat, 2 Mar 2013 15:09:48 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1UBo4C-00021B-6W; Sat, 02 Mar 2013 16:09:40 +0100 Received: from h253044.upc-h.chello.nl ([62.194.253.44] helo=pinky) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UBo4C-0005vE-5c; Sat, 02 Mar 2013 16:09:40 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Ben Morrow" , "Daniel Eischen" Subject: Re: Musings on ZFS Backup strategies References: <20130301165040.GA26251@anubis.morrow.me.uk> <20130301185912.GA27546@anubis.morrow.me.uk> Date: Sat, 02 Mar 2013 16:09:41 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.14 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.8 X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.1 X-Scan-Signature: d3d6c6694e059b137bd8e4e2c0542d46 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 15:09:49 -0000 On Fri, 01 Mar 2013 21:34:39 +0100, Daniel Eischen wrote: > On Fri, 1 Mar 2013, Ben Morrow wrote: > >> Quoth Daniel Eischen : >>> >>> Yes, we still use a couple of DLT autoloaders and have nightly >>> incrementals and weekly fulls. This is the problem I have with >>> converting to ZFS. Our typical recovery is when a user says >>> they need a directory or set of files from a week or two ago. >>> Using dump from tape, I can easily extract *just* the necessary >>> files. I don't need a second system to restore to, so that >>> I can then extract the file. >> >> As Karl said originally, you can do that with snapshots without having >> to go to your backups at all. With the right arrangements (symlinks to >> the .zfs/snapshot/* directories, or just setting the snapdir property to >> 'visible') you can make it so users can do this sort of restore >> themselves without having to go through you. > > It wasn't clear that snapshots were traversable as a normal > directory structure. I was thinking it was just a blob > that you had to roll back to in order to get anything out > of it. That is the main benefit of snapshots. :-) You can also very easily diff files between them. Mostly a lot of data is static so it does not cost a lot to keep snapshots. There are a lot of scripts online and in ports which make a nice retention policy like e.g. 7 daily snaphots, 8 weekly, 12 monthly, 2 yearly. See below for (an incomplete list of) what I keep about my homedir at home. > Under our current scheme, we would remove snapshots > after the next (weekly) full zfs send (nee dump), so > it wouldn't help unless we kept snapshots around a > lot longer. Why not. > Am I correct in assuming that one could: > > # zfs send -R snapshot | dd obs=10240 of=/dev/rst0 > > to archive it to tape instead of another [system:]drive? Yes, your are correct. The manual page about zfs send says: 'The format of the stream is committed. You will be able to receive your streams on future versions of ZFS.' Ronald. tank/home 115G 65.6G 53.6G /home tank/home@auto-2011-10-25_19.00.yearly 16.3G - 56.8G - tank/home@auto-2012-06-06_22.00.yearly 5.55G - 53.3G - tank/home@auto-2012-09-02_20.00.monthly 2.61G - 49.3G - tank/home@auto-2012-10-15_06.00.monthly 2.22G - 49.9G - tank/home@auto-2012-11-26_13.00.monthly 2.47G - 50.2G - tank/home@auto-2013-01-07_13.00.monthly 2.56G - 51.5G - tank/home@auto-2013-01-21_13.00.weekly 1.06G - 52.4G - tank/home@auto-2013-01-28_13.00.weekly 409M - 52.3G - tank/home@auto-2013-02-04_13.00.monthly 625M - 52.5G - tank/home@auto-2013-02-11_13.00.weekly 689M - 52.5G - tank/home@auto-2013-02-16_13.00.weekly 17.7M - 52.5G - tank/home@auto-2013-02-17_13.00.daily 17.7M - 52.5G - tank/home@auto-2013-02-18_13.00.daily 17.9M - 52.5G -