From owner-freebsd-fs@FreeBSD.ORG Mon Apr 18 20:15:19 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 7783C106564A for ; Mon, 18 Apr 2011 20:15:19 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4DE8FC1E for ; Mon, 18 Apr 2011 20:15:18 +0000 (UTC) Received: by qwc9 with SMTP id 9so3142882qwc.13 for ; Mon, 18 Apr 2011 13:15:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Me0DG089EUD4JA+s8dETYGRbcXXC2MdUM/uJOGm+DTs=; b=rVNYw9OrcMLtObpya+Wf/96cuvzFFW+0swIC2wc/PwA5xShexAiGZes+v6B8FSRZZ6 EXVZ14xCe7zjUouJHmhjmAlBMo18LiijFZbtANxZg/wqSQbw3Hzv3FezZqcYv72QfTkl 4LCF/LTvXc9GUDH8z4hOeoQCH9TjHcpsGX6Oc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=x448twjE5r1OpjCZtTzh9ysJAuT3Pd4sj/juruPFxRib3nUBHXYWwidug/y8gkcGRC 8KwimaSwzbQoXR6I2k0LxudPosWVFhrzbgGLvTi3nmThHkEcPM0pHIV+N/P85SvPh5lW 9be0wae1fXRyvZEb7p4ybaz9V9R+rPIY0W48w= MIME-Version: 1.0 Received: by 10.229.227.3 with SMTP id iy3mr4324817qcb.38.1303157718100; Mon, 18 Apr 2011 13:15:18 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.229.221.193 with HTTP; Mon, 18 Apr 2011 13:15:17 -0700 (PDT) In-Reply-To: <4DAC96EA.8080505@ukr.net> References: <4DAC7811.3090407@ukr.net> <4DAC96EA.8080505@ukr.net> Date: Mon, 18 Apr 2011 13:15:17 -0700 X-Google-Sender-Auth: MNrnxsseObBBdMd_p7x1I2ls_hQ Message-ID: From: Artem Belevich To: "Vladislav V. Prodan" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: Prompt to synchronize two volumes ZFS 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: Mon, 18 Apr 2011 20:15:19 -0000 On Mon, Apr 18, 2011 at 12:54 PM, Vladislav V. Prodan wrote: > 18.04.2011 21:12, Artem Belevich wrote: >> >> This page outlines ZFS replication process fairly well: >> http://wikitech-static.wikimedia.org/articles/z/f/s/Zfs_replication.html > > I do not understand why dumps snapshot to a file and then deploy on a remote > machine? > You can not like something is poured snapshot to another server? > > zfs send -i export/upload@zrep-00001 export/upload@zrep-00002 | ssh > otherservername "cat > /export/save/upload@zrep-00002" > cat /export/save/upload@rzrepl-00002 | zfs recv export/upload > > Maybe there are some pitfalls? They mentioned performance. mbuffer in-between receive and send makes *a lot* of difference as long as you provide few seconds worth of buffering at the rate your filesystems can sustain. I think the authors of the page above just didn't use large enough buffer. You would probably have to experiment yourself. In my case of ~3TB transfer (mostly large files), I ended up with "mbuffer -m512M". I also used mbuffer's built-in network transfer mechanism (see mbuffer's -I/-O options) as at high data rates ssh became the bottleneck. --Artem