From owner-freebsd-questions@freebsd.org Wed Jun 1 20:01:11 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 380DCB60D58 for ; Wed, 1 Jun 2016 20:01:11 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: from mail-it0-f48.google.com (mail-it0-f48.google.com [209.85.214.48]) (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 0FDD81EEB for ; Wed, 1 Jun 2016 20:01:10 +0000 (UTC) (envelope-from brandon.wandersee@gmail.com) Received: by mail-it0-f48.google.com with SMTP id z189so92040394itg.0 for ; Wed, 01 Jun 2016 13:01:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=+93ibdzatmzOVw6lwUaS7c4H2tITZ2wNV1w7lMq3Izs=; b=EnoFnLKpxXb3Cb7CaymgtBjSk1QzXde2yO2UKoA/S4hlYr6CxrnvpzVyyF+Em3iqAB vWs/aRrGfmpm6dDPD9ppLPQVHuXeO3rqWDUEJxR9yKYX04kpJ58s9pICWCQX2BKp2MYO UngKAOCYC7NY97b69ZqvQGBXgJH7WPK0X64iiAUKj4szUDBZEN+BBdw8xGNVgyuQVin7 wVFa3MNqlWukIPCFBsEEEhWVIr4fV74M8zzcXeoIQKtZcwKKa1+zU7eeZj7Z3Sle1HCP cAszmXiEIbzPDJrQ8eyCXuZiYB8ADTe9uRxKpdRhK6FDUdUJhFLS/vWwgI54N2+sUWvy xpYw== X-Gm-Message-State: ALyK8tLZOZMrijFKdvKdydwpK40CB2MGoRJGp5TypsEwYBXngp7Oq0Jan2IWFCDvf4gpFg== X-Received: by 10.36.17.207 with SMTP id 198mr22538680itf.81.1464805130861; Wed, 01 Jun 2016 11:18:50 -0700 (PDT) Received: from WorkBox.Home.gmail.com (63-231-128-37.mpls.qwest.net. [63.231.128.37]) by smtp.gmail.com with ESMTPSA id k72sm12676212ita.17.2016.06.01.11.18.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Jun 2016 11:18:49 -0700 (PDT) References: <20160601113332.5e250d300d770ab04e9c9cc2@sohara.org> User-agent: mu4e 0.9.16; emacs 24.5.1 From: Brandon J. Wandersee To: Steve O'Hara-Smith Cc: Luca Ferrari , freebsd-questions Subject: Re: rsync or git backups? In-reply-to: <20160601113332.5e250d300d770ab04e9c9cc2@sohara.org> Date: Wed, 01 Jun 2016 13:18:43 -0500 Message-ID: <86k2i8kc1o.fsf@WorkBox.Home> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 20:01:11 -0000 Steve O'Hara-Smith writes: > On Wed, 1 Jun 2016 10:35:06 +0200 > Luca Ferrari wrote: > >> Hi all, >> so far I'm using rsync to keep in sync a couple of removable media >> (well, up to four) where one is the "master" and the others are a >> cascade backups (meaning they are set at different time). >> So far so good. >> One problem is that I tend to change things in the master, e.g., bulk >> file renaming or moving, so when I replicate it on the backups I have >> to force the deletion of no more existing content. >> This approach, however, relies on the fact that the master is good. My >> fear is that if the master corrupts some file, I could possibly loss >> them if they have also been moved since I will no more be able to >> recognize them on the slaves. >> >> So I would like to have some feature like git (or fossil) for hash >> handling, but since I'm talking about 290+ GB of binaries I'm not sure >> this approach could work. >> >> Any suggestion? > > Use ZFS with snapshots (the zfs-periodic package is good for this) > and replace the rsync with send/receive, ZFS will protect you from hardware > silent corruption (provided you allow some redundancy - use copies on pools > with no redundancy) while the snapshots will protect you from mistakes. If ZFS seems like overkill or too much hassle at the moment, you could instead use sysutils/rsnapshot. It uses rsync to create snapshot-style, rotating, de-duplicating, incremental backups. Verbose logging will show you what files have changed since the last backup, so if you see a file in the logs that you know you haven't changed in some time, it's probably corrupt or has otherwise been compromised. Meanwhile, the previous (good) versions will remain intact. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------