From owner-freebsd-stable@FreeBSD.ORG Mon Mar 4 16:07:40 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 73A7C176 for ; Mon, 4 Mar 2013 16:07:40 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-bk0-f51.google.com (mail-bk0-f51.google.com [209.85.214.51]) by mx1.freebsd.org (Postfix) with ESMTP id 0539436F for ; Mon, 4 Mar 2013 16:07:39 +0000 (UTC) Received: by mail-bk0-f51.google.com with SMTP id ik5so2514539bkc.10 for ; Mon, 04 Mar 2013 08:07:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LhhCXONZ4ZSz0nmMfkq6k7xWhim+LDrw+y6YJhE+Dfs=; b=eNvBmBl5NUZyNdTxGfCNdUxbtm1RLzFaRYJVXZyAWvdKo4TKGRL+CxsXiBBMPgcDYp ca/8jrJPYW6OGCJ2IsFKs75AJhnZ6ZZJSXy4/Qde7aQEcceCrWdgz7lsKtq+ebkaggwd 3TXF4pMDN+SrE2TNUR+62YDvLyi2D7nwVa1qDY42zenc3i+xe9Idpfl2yd70JcZsHLTy r1SA/9y8WvoAPinkKdODLdz4qnY64Tfak+PwuKh5k4Gsq6Rx/bDA5epSlTZ8CzGRq4z5 Qz0UeHna+qaXk120mxCPCIUOGl0YtMyMHdbDg1RuIfjSs5o0S7dL5CaX6y+MzGl0vqgY CAkA== X-Received: by 10.205.123.138 with SMTP id gk10mr7748655bkc.49.1362413253322; Mon, 04 Mar 2013 08:07:33 -0800 (PST) Received: from [192.168.1.128] ([91.196.229.122]) by mx.google.com with ESMTPS id x10sm6028582bkv.13.2013.03.04.08.07.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Mar 2013 08:07:32 -0800 (PST) Message-ID: <5134C6C2.9020009@gmail.com> Date: Mon, 04 Mar 2013 18:07:30 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:19.0) Gecko/20100101 Firefox/19.0 SeaMonkey/2.16 MIME-Version: 1.0 To: David Magda Subject: Re: Musings on ZFS Backup strategies References: <5130BA35.5060809@denninger.net> <5130EB8A.7060706@gmail.com> <2B318078-F863-4415-8DAE-94EE4431BF4C@ee.ryerson.ca> In-Reply-To: <2B318078-F863-4415-8DAE-94EE4431BF4C@ee.ryerson.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Mon, 04 Mar 2013 16:07:40 -0000 02.03.2013 03:12, David Magda: > > On Mar 1, 2013, at 12:55, Volodymyr Kostyrko wrote: > >> Yes, I'm working with backups the same way, I wrote a simple script that synchronizes two filesystems between distant servers. I also use the same script to synchronize bushy filesystems (with hundred thousands of files) where rsync produces a too big load for synchronizing. >> >> https://github.com/kworr/zfSnap/commit/08d8b499dbc2527a652cddbc601c7ee8c0c23301 > > There are quite a few scripts out there: > > http://www.freshports.org/search.php?query=zfs A lot of them require python or ruby, and none of them manages synchronizing snapshots over network. > For file level copying, where you don't want to walk the entire tree, here is the "zfs diff" command: > >> zfs diff [-FHt] snapshot [snapshot|filesystem] >> >> Describes differences between a snapshot and a successor dataset. The >> successor dataset can be a later snapshot or the current filesystem. >> >> The changed files are displayed including the change type. The change >> type is displayed useing a single character. If a file or directory >> was renamed, the old and the new names are displayed. > > http://www.freebsd.org/cgi/man.cgi?query=zfs > > This allows one to get a quick list of files and directories, then use tar/rsync/cp/etc. to do the actual copy (where the destination does not have to be ZFS: e.g., NFS, ext4, Lustre, HDFS, etc.). I know that but I see no reason in reverting to file-based synch if I can do block-based. -- Sphinx of black quartz, judge my vow.