From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to build a time machine on Gentoo
Date: Wed, 18 Aug 2010 19:59:16 +0800 [thread overview]
Message-ID: <1282132756.8488.23.camel@rattus> (raw)
In-Reply-To: <AANLkTimKHhepWwtwedk_Li3RzywV2E2s0GqZhLw7U+3-@mail.gmail.com>
On Wed, 2010-08-18 at 14:09 +0300, Nganon wrote:
>
>
> On 17 August 2010 22:34, Enrico Weigelt <weigelt@metux.de> 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
next prev parent reply other threads:[~2010-08-18 11:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 23:11 [gentoo-user] How to build a time machine on Gentoo Nganon
2010-08-16 0:15 ` Alex Schuster
2010-08-16 10:27 ` Nganon
2010-08-16 8:36 ` Marco
2010-08-16 10:30 ` Nganon
2010-08-16 21:37 ` Mick
2010-08-16 23:53 ` Thomas Yao
2010-08-17 11:34 ` Nganon
2010-08-17 11:29 ` Nganon
2010-08-17 12:14 ` Maximilian Bräutigam
2010-08-17 12:33 ` Alex Schuster
2010-08-18 11:04 ` Nganon
2010-08-18 11:34 ` Neil Bothwick
2010-08-18 11:53 ` Nganon
2010-08-18 14:53 ` Bill Longman
2010-08-18 18:03 ` Nganon
2010-08-18 18:37 ` Bill Longman
2010-08-18 18:49 ` Joerg Schilling
2010-08-18 19:04 ` Nganon
2010-08-18 19:28 ` Joerg Schilling
2010-08-18 19:09 ` Bill Longman
2010-08-18 19:29 ` Alan McKinnon
2010-08-18 20:03 ` Joerg Schilling
2010-08-19 9:30 ` Joerg Schilling
2010-08-18 18:53 ` Nganon
2010-08-17 19:34 ` Enrico Weigelt
2010-08-18 11:09 ` Nganon
2010-08-18 11:59 ` William Kenworthy [this message]
2010-08-18 17:56 ` Nganon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1282132756.8488.23.camel@rattus \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox