From owner-freebsd-questions@freebsd.org Wed Dec 21 01:41:43 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD058C8961F for ; Wed, 21 Dec 2016 01:41:43 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-it0-f47.google.com (mail-it0-f47.google.com [209.85.214.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B22ED1289 for ; Wed, 21 Dec 2016 01:41:43 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-it0-f47.google.com with SMTP id 75so70207191ite.1 for ; Tue, 20 Dec 2016 17:41:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=KQvqOV3Ju9D0jPfv7ji/4O6YIKZoBj1AbYcaRCluMx8=; b=mTV7kljv2lW6pbP8vM5gZTtRLJN2CbDO96ZRvsgPJ/hPFK+jmu9jZklZjBuryGsEC6 0DAz4FsGbsItDlnP11Hvsio7Il1j9I8nyRK5yfmgTB+u5IlPCgCHYTD/tB3YEuEOYlVy WyNzZfsi1eqjGi1ChemQ+NMfmGIoUb0piq6iSY3GA7EPfi4QjwAkLhI+J7s2sBm9ey3z vyHMI4naB/BmRM6oKTvMNu11znNZ4j8hIiaGzlbOzJcSAoCEJQa1D6qgMDllDx75+gFK m/+tXXnvyGRvAzZr6ctxFKAX1MaOPVQJv60pItQfSrZerwA5uh1s9PfYMAGt37cFKcwE MptA== X-Gm-Message-State: AIkVDXKIMzB/n3BwkHcxB3Sar7o4fA5honjtCDfl1pp4sh+iCBhxt09GPLU2iiLZ9DZimQ== X-Received: by 10.36.123.82 with SMTP id q79mr5564610itc.25.1482284496498; Tue, 20 Dec 2016 17:41:36 -0800 (PST) Received: from WorkBox.homestead.org (65-128-151-1.mpls.qwest.net. [65.128.151.1]) by smtp.gmail.com with ESMTPSA id j143sm7147450ita.1.2016.12.20.17.41.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Dec 2016 17:41:35 -0800 (PST) Received: from localhost (WorkBox.homestead.org [local]) by WorkBox.homestead.org (OpenSMTPD) with ESMTPA id ce37dfef; Tue, 20 Dec 2016 19:41:33 -0600 (CST) References: <867f6u22vv.fsf@gmail.com> User-agent: mu4e 0.9.16; emacs 25.1.1 From: Brandon J. Wandersee To: Malcolm Matalka Cc: Aleksandr Miroslav , freebsd-questions@freebsd.org Subject: Re: zfs (zxfer) replication -- "holes" in backups? In-reply-to: <867f6u22vv.fsf@gmail.com> Date: Tue, 20 Dec 2016 19:41:33 -0600 Message-ID: <86bmw6m52q.fsf@WorkBox.homestead.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2016 01:41:44 -0000 Malcolm Matalka writes: > Aleksandr Miroslav writes: >> It turns out that when I sent my snapshots to my backup machine, I never >> turned off this property, the backup machine also had zfstools installed, >> and so was taking snapshots of my backupsnaphots. Hence the holes. I've >> since cleaned this up, and will let backups run for a few days and see if >> this fixes the problem. > > I ran into this problem where the snapshots the machine that was backing > up to named the snapshots the same thing so zxfer thought the transfer > didn't need to happen. I "solved" this by putting the hostname in the > snapshot name. There is probably a better way though. I'm not sure there's an entirely elegant way to deal with it. I use zfstools and zxfer myself, and have just accepted having a really long line in the crontab to remove the properties before transfer. I used to use sysutils/zfsnap, which is a pretty good tool in its own right and can avoid the problem of the system holding backups creating new snapshots on the backups. However, it does that by requiring multi-entries for each type of backup iteration, as well as lines for every single dataset, added to /etc/periodic.conf. Works well enough for simple setups, but more complex ones get out of hand. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------