From owner-freebsd-questions@FreeBSD.ORG Tue Jan 8 20:24:36 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 170F91F7 for ; Tue, 8 Jan 2013 20:24:36 +0000 (UTC) (envelope-from schultz@ime.usp.br) Received: from hermes.ime.usp.br (hermes.ime.usp.br [143.107.45.4]) by mx1.freebsd.org (Postfix) with ESMTP id CA294984 for ; Tue, 8 Jan 2013 20:24:35 +0000 (UTC) Received: from arachne.ime.usp.br (arachne.ime.usp.br [143.107.45.22]) by hermes.ime.usp.br (Postfix) with ESMTP id 561EC8003F069 for ; Tue, 8 Jan 2013 18:24:24 -0200 (BRST) Received: by arachne.ime.usp.br (Postfix, from userid 112) id 43736361252; Tue, 8 Jan 2013 18:24:24 -0200 (BRST) Received: from bd65dbab.virtua.com.br (bd65dbab.virtua.com.br [189.101.219.171]) by webmail.ime.usp.br (Horde Framework) with HTTP; Tue, 08 Jan 2013 18:24:24 -0200 Message-ID: <20130108182424.18980pw5cytz6gl4@webmail.ime.usp.br> Date: Tue, 08 Jan 2013 18:24:24 -0200 From: schultz@ime.usp.br To: freebsd-questions@freebsd.org Subject: Re: Backup with mtree and rsync? References: <20130105161256.49797e7viwwtqfc8@webmail.ime.usp.br> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.10) X-Horde-Username: schultz X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on hermes.ime.usp.br X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2013 20:24:36 -0000 I apparently reinvented the wheel. :-) Thanks for the link, it is indeed very inspiring. Quoting Ciprian Dorin Craciun : > On Sat, Jan 5, 2013 at 8:12 PM, wrote: >> I have been wondering whether it is possible to create a backup system >> using mtree and rsync. Essentially, the user would create a mtree >> specification of the source directory and copy it over to the destination >> directory with rsync. Any changes in the destination could then be >> detected before restoring with the mtree specification, which should >> contain strong hashes of the files and should not contain the nlink >> keyword. > > > A little bit off-topic, but there is a small tool that does > something similar to your suggested `mtree` usage, but specifically > tailored for backups, `rdup`: > > http://miek.nl/projects/rdup > > Although I've not used it myself (I use `rdiff-backup` and on > Linux), the idea is pretty similar with what you want to achieve: > * you run `rdup` with an old "descriptor file" plus a target path, > and in turn it generates: > * a new "descriptor file"; > * a list of files that should be backed up; > * you then decide what you do with the list of files to be > backed-up (i.e. put them in a `tar`, `rysnc` them to a server, etc.); > > Hope it helps, > Ciprian. >