From: Christian Kellermann <Christian.Kellermann@nefkom.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] How to maintain a venti server
Date: Wed, 18 Apr 2007 14:23:02 +0200 [thread overview]
Message-ID: <20070418122302.GO13972@hermes.my.domain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
Dear list,
After reading through the venti paper and the relevant manpages some
questions still prevail:
+ How can I check the status of my venti server easily? The only
option I could find is reading through ventis status pages. Although
I couldn't read from that with abaco or hget...
+ How can I archive my venti? Heiko on this list mentioned burning
the arenas to a disk. Is there something like dump9660 for this? As
dump9660 works on a file basis only I guess it cannot be used.
+ Am I supposed to run maintenance tasks of ventiaux(8) on a regular
basis? If yes when and which?
+ I want to use a venti server as backup server for a some machines
in my network, plan9 and others. What are my best options? I thought
about using p9p's vac to copy the other machine's backups to venti, but I
would like to make them available again through a nice directory
structure a la dumpfs on the plan9 server. (Which in turn
could be exported via nfs)
Thanks for your thoughts!
Christian
--
You may use my gpg key for replies:
pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2007-04-18 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 12:23 Christian Kellermann [this message]
2007-04-18 13:32 ` Steve Simon
2007-04-18 16:39 ` Russ Cox
2007-04-18 23:02 ` Steve Simon
2007-04-18 16:57 ` geoff
2007-04-18 18:07 ` Skip Tavakkolian
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=20070418122302.GO13972@hermes.my.domain \
--to=christian.kellermann@nefkom.net \
--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).