9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil+venti backup question
Date: Thu, 29 Mar 2007 14:05:47 +0200	[thread overview]
Message-ID: <48c1427b41bdcab1d54e6b66bef94d79@voidness.de> (raw)
In-Reply-To: <7e3fd128dbab5024ffb891711b1cf076@coraid.com>

> On Thu Mar 29 07:12:11 EDT 2007, uriel99@gmail.com wrote:
>> Yes, but then you wont have permanent snapshots, I very much recommend
>> using venti, among other reasons because even in case of your fossil
>> getting corrupted (which is not unheard of, specially if you run out
>> of space), you can always restore the last snap from venti.
> 
> the solution to fossil corrupting itself is to fix fossil, not to 
> insist on venti.
> 
> automatic archival snapshots are a great feature, but my personal 
> experience has been that venti is not resistant to unexpected
> power failure.

Besides the archival snapshots, the other nice feature of venti is the
partitioning in CD-sized arenas.  Having every used arena written to
CD, one can stay quite calm, even if venti suffers a power failure.

I write the latest arena onto CD in a daily cron job, periodically
cmp'ing the CD set with the arenas.

Heiko



  reply	other threads:[~2007-03-29 12:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 11:03 bituman
2007-03-29 11:11 ` Uriel
2007-03-29 11:47   ` erik quanstrom
2007-03-29 12:05     ` Heiko Dudzus [this message]
2007-04-18 12:11       ` Christian Kellermann
2007-03-29 11:22 ` erik quanstrom
2007-03-29 11:42   ` bituman
2007-03-29 11:56     ` erik quanstrom
2007-03-29 12:06       ` bituman
2007-03-29 12:25         ` erik quanstrom
2007-03-30  6:23 YAMANASHI Takeshi
2007-03-30  8:34 ` bituman
2007-03-30  8:45   ` Charles Forsyth
2007-03-30  7:52     ` Federico G. Benavento

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=48c1427b41bdcab1d54e6b66bef94d79@voidness.de \
    --to=heiko.dudzus@gmx.de \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).