From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Anyone using p9p or Plan 9 venti as a more generic backup system?
Date: Wed, 17 Nov 2010 09:24:23 -0800 [thread overview]
Message-ID: <AANLkTi=Lz1FhmCKr901=p4EwLo6naR9TrsxZRfetRmAj@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=DOUSD+hWOOA069wkkEEKapOrzbTeLA9jDh7uF@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On Wed, Nov 17, 2010 at 9:14 AM, Venkatesh Srinivas <me@acm.jhu.edu> wrote:
> On Wed, Nov 17, 2010 at 11:51 AM, David Leimbach <leimy2k@gmail.com>
> wrote:
> > I'm giving consideration to maintaining a venti-based setup for my house
> for
> > all the digital media we have (since getting our Apple TV, we've had more
> > stuff to stream around the house).
> > I've just now started playing with things like vac/unvac, to backup and
> > extract trees of my HFS+ file system and I wonder about a few things.
> > What do people do if they ever lose their venti scores? Seems like this
> is
> > "handle-less" data now, and fairly useless.
> > I figure I could keep a vac archive of venti scores, then I'd only need
> to
> > "remember" one, and name the files I store the scores in reasonably, but
> if
> > that's lost... what are my options?
> > Dave
>
> There is a script floating around (dumpvacroots or somesuch) that lets
> you recover vac scores given access to the venti arenas.
>
> I'd be very careful with vac -m and -a on Unix; both have been at the
> root of considerable data-loss on a unix venti for me. I'd recommend
> vac-ing tarballs, rather than using vac's on unix trees directly. But
> your mileage may vary...
>
This is mainly a form of secondary backup for me for now, but given what I
learn about it over time, it could become a primary.
Are there any open problem reports around this? I might be interested in
tackling some of these, or at least trying to reproduce them.
I still do some rsync based backups anyway.
>
> -- vs
>
>
[-- Attachment #2: Type: text/html, Size: 2365 bytes --]
next prev parent reply other threads:[~2010-11-17 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:51 David Leimbach
2010-11-17 17:14 ` Venkatesh Srinivas
2010-11-17 17:23 ` dexen deVries
2010-11-17 17:43 ` Venkatesh Srinivas
2010-11-17 17:44 ` David Leimbach
2010-11-18 19:40 ` Bakul Shah
2010-11-18 19:44 ` dexen deVries
2010-11-17 17:24 ` David Leimbach [this message]
2010-11-22 15:56 ` Latchesar Ionkov
2010-11-22 20:35 ` David Leimbach
2010-11-23 4:21 ` Anthony Sorace
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='AANLkTi=Lz1FhmCKr901=p4EwLo6naR9TrsxZRfetRmAj@mail.gmail.com' \
--to=leimy2k@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).