From owner-freebsd-fs@FreeBSD.ORG Thu Dec 1 10:44:17 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 721001065673 for ; Thu, 1 Dec 2011 10:44:17 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 199E18FC18 for ; Thu, 1 Dec 2011 10:44:16 +0000 (UTC) Received: by yenq9 with SMTP id q9so2424129yen.13 for ; Thu, 01 Dec 2011 02:44:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2viTJKtsN3j+G/+Igln7Ptp8jLhTosc/Q6MGxE4Lu0c=; b=DdvKa6XY40PKUb5vtXYffDZo1zZ8T2FNycnIjOm43b/X08B4f/y0EUoy7tw5rp7Yq2 SD9HzW7+1ocOlWb2Dddg4oVecdRJ7MXCcEiJ6qktj8VueK7MWJU23KQ0QyNgon1jLQnl iRWPN/qBFOcvZJrQ5ks5xtN5CYOtCx8ksiAwI= MIME-Version: 1.0 Received: by 10.236.155.36 with SMTP id i24mr10361237yhk.43.1322734818286; Thu, 01 Dec 2011 02:20:18 -0800 (PST) Received: by 10.236.95.41 with HTTP; Thu, 1 Dec 2011 02:20:18 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Dec 2011 10:20:18 +0000 Message-ID: From: krad To: Techie Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS dedup and replication 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: Thu, 01 Dec 2011 10:44:17 -0000 On 28 November 2011 23:01, Techie wrote: > Hi all, > > Is there any plans to implement sharing of the ZFS DDT Dedup table or > to make ZFS aware of the destination duplicate blocks on a remote > system? > > >From how I understand it, the zfs send/recv stream does not know about > the duplicated blocks on the receiving side when using zfs send -D -i > to sendonly incremental changes. > > So take for example I have an application that I backup each night to > a ZFS file system. I want to replicate this every night to my remote > site. Each night that I back up I create a tar file on the ZFS data > file system. When I go to send an incremental stream it sends the > entire tar file to the destination even though over 90% of those > blocks already exist at the destination.. Is there any plans to make > ZFS aware of what exists already at the destination site to eliminate > the need to send duplicate blocks over the wire? zfs send -D I believe > only eliminates the duplicate blocks within the stream. > > Perhaps I am wrong.. > > > Thanks > Jimmy > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > Why tar up the stuff? Just do a zfs snap and then you bypass the whole issue?