From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] venti backup
Date: Tue, 17 Jan 2012 14:04:04 +0100 [thread overview]
Message-ID: <20120117140404.04923461@wks-ddc.exosec.local> (raw)
In-Reply-To: <CAFo14L1+rdfj7xt3D+EYPZJseTD54908ac-FG7ncOw3bCKyTTA@mail.gmail.com>
> I've backed up all my *active* arenas in to another disk, just to be
> safe. The man page says that the index and the bloom filter may be
> rebuilt if lost. So it seems sufficient to backup my arenas, am I
> right?
Yes, you can rebuild the index and the Bloom filter
with 'venti/buildindex -b'.
--
David du Colombier
next prev parent reply other threads:[~2012-01-17 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 12:34 hugo rivera
2012-01-17 13:02 ` Steve Simon
2012-01-17 13:14 ` hugo rivera
2012-01-17 13:04 ` David du Colombier [this message]
2012-01-19 16:11 ` hugo rivera
2012-01-19 16:45 ` David du Colombier
2012-01-19 23:04 ` David du Colombier
2012-01-20 11:03 ` hugo rivera
2012-01-20 15:02 ` David du Colombier
2012-01-20 17:04 ` hugo rivera
2012-01-20 18:19 ` David du Colombier
2012-01-20 19:10 ` hugo rivera
2012-01-20 22:39 ` David du Colombier
2012-01-23 10:28 ` hugo rivera
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=20120117140404.04923461@wks-ddc.exosec.local \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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).