From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OlhJ8-0007Qu-8Z for garchives@archives.gentoo.org; Wed, 18 Aug 2010 11:59:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 92392E085A; Wed, 18 Aug 2010 11:59:25 +0000 (UTC) Received: from outbound.icp-qv1-irony-out2.iinet.net.au (outbound.icp-qv1-irony-out2.iinet.net.au [203.59.1.107]) by pigeon.gentoo.org (Postfix) with ESMTP id 8EBB5E085A for ; Wed, 18 Aug 2010 11:59:24 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqgFAOJna0x8qebx/2dsb2JhbACTMY0Zcb5NhTcEhC+IOg X-IronPort-AV: E=Sophos;i="4.56,227,1280678400"; d="scan'208";a="685338730" Received: from unknown (HELO moriah.localdomain) ([124.169.230.241]) by outbound.icp-qv1-irony-out2.iinet.net.au with ESMTP; 18 Aug 2010 19:59:20 +0800 Received: from localhost (localhost [127.0.0.1]) by moriah.localdomain (Postfix) with ESMTP id 552831D68139 for ; Wed, 18 Aug 2010 19:59:20 +0800 (WST) X-Virus-Scanned: amavisd-new at localdomain Received: from moriah.localdomain ([127.0.0.1]) by localhost (moriah.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d39mXEWim9IZ for ; Wed, 18 Aug 2010 19:59:16 +0800 (WST) Received: from [192.168.44.2] (rattus [192.168.44.2]) by moriah.localdomain (Postfix) with ESMTP id C667B1D68136 for ; Wed, 18 Aug 2010 19:59:16 +0800 (WST) Subject: Re: [gentoo-user] How to build a time machine on Gentoo From: William Kenworthy To: gentoo-user@lists.gentoo.org In-Reply-To: References: <20100817193426.GA6494@nibiru.local> Content-Type: text/plain; charset="ISO-8859-1" Organization: Home in Perth! Date: Wed, 18 Aug 2010 19:59:16 +0800 Message-ID: <1282132756.8488.23.camel@rattus> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit X-Archives-Salt: 48f03eca-dd6c-4504-ac9c-86b3c8693d2b X-Archives-Hash: eae08e7ae50d827980e8677eb0f4378b On Wed, 2010-08-18 at 14:09 +0300, Nganon wrote: > > > On 17 August 2010 22:34, Enrico Weigelt wrote: > For things I'd like to keep an history (eg. /etc) I'm using > git, and > pushing the repo to a remote server (denying non-fastfoward > updates > there, so an theorectical highjacker cannot destroy my > history) > > > Using git for /etc is a great idea. > Thanks. > Another option is: * app-backup/dirvish Latest version available: 1.2.1 Latest version installed: 1.2.1 Size of downloaded files: 47 kB Homepage: http://www.dirvish.org/ Description: Dirvish is a fast, disk based, rotating network backup system. License: OSL-2.0 Works by first creating a copy (--init) and then hard-linking subsequent versions of files/directories back to the original original if its identical. If a file is changed/new, it is copied instead of linked so actual space usage quickly stabilises even with a varying number of versions. Backup over the network (this is how I have configured mine) uses rsync over ssh with keys and is "pull" from a cron job on the backup server or manual on demand (i.e., server initiated). Version management is by a reasonably sophisticated date of version scheme where by running "dirvish-expire" deletes out of date versions (runs in a cron job). The smart part is that once the last hard link to file is deleted, its gone, otherwise its kept in the remaining versions :) Restore is a simple matter of identifying the version you want and copying it back - Ive restored individual files through to complete systems after total disk failure. Can do includes/excludes, whole systems or just directories such as /etc and can be easily automated. Doesnt use compression, but most backup regimes (every day for a weekly rota + a Sunday kept for 6 months) stabilise at about 2x the original (gross) copy size, no matter how many copies with average changes between versions. Though large scale changes such as an "emerge -e world" will take more as it will generate new copies of most files. Downside is it will hammer the destination file system - reiserfs3 works well, ext2/ext3 have been hopeless everytime I've tried - mass corruption. The file system will need a large number of inodes (for links) if there are an excessive number of files x versions - again reiserfs3 scores well here. Highly recommended! BillK