9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <knapjack@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 killer applications?
Date: Wed, 17 Nov 2004 19:54:37 -0800	[thread overview]
Message-ID: <6e35c06204111719543e8d6657@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.58.0411171554530.6130@malasada.lava.net>

On Wed, 17 Nov 2004 15:56:05 -1000 (HST), Tim Newsham <newsham@lava.net> wrote:
> So dont put the files in venti?  Seems like the ideal mix is
> venti for long-lived important documents and something else
> for files that turn over more often or require a short lifetime.

The problem with some of the document retention standards is the
nebulous definition of what needs to be kept.

For instance, where I live the state requires any documents that
communicate daily schedules of state-funded employees or
communications regarding policy or working/draft policy to be kept for
(I think) three years.

Because bureaucrats and not geeks set the standards, we're left
wondering how often one should snapshot, say, calendar data in
Exchange to ensure that transient changes in schedules are kept at a
best-effort level to meet state standards.  We archive all mail sent
and received to alleviate the need to content-filter email for
differing 3-, 5- or 7-year standards, just as many companies bound by
the SEC now archive all instant message traffic regardless of content.

The beauty of a system like venti is that the minimal amount of space
is used for redundant data regardless of name, organizational change
or timestamp, and it relieves the archiver from deciding what is
important and what isn't.  Though copyright-infringing data is
troublesome in a permanent archive, it's exactly the reason to archive
(nearly) everything when bound by stringent rules -- to ensure the
rules are followed and to easily track compliance.

Watching people implement various document retention standards on
various platforms really makes you appreciate the simplicity and
cost-effectiveness of venti as a possible solution.  A handy vac
client for commercial platforms set to a specific schedule by policy
would be a "killer app" for many organizations.

-Jack

A little light reading:
http://techrepublic.com.com/5100-6315_11-5054924.html
http://www.cio.com/archive/031503/tl_washington.html

A solution:
http://www.alphaworks.ibm.com/tech/vitalfileretention

A bureaucratic example:
http://www.secstate.wa.gov/archives/pdf/School%20Districts%20March%202003.pdf


  reply	other threads:[~2004-11-18  3:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 15:33 Brantley Coile
2004-11-17 16:51 ` Matthias Teege
2004-11-17 17:52 ` Jack Johnson
2004-11-17 18:06   ` Dave Lukes
2004-11-17 23:16   ` geoff
2004-11-18  0:06     ` Jack Johnson
2004-11-18  5:32       ` vdharani
2004-11-18  1:56         ` Tim Newsham
2004-11-18  3:54           ` Jack Johnson [this message]
2004-11-18  0:59 ` Kenji Okamoto
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 17:25 Benjamin Huntsman
2004-11-17 20:34 ` Vester Thacker
2004-11-16 21:24 Benjamin Huntsman
2004-11-16 16:07 David Leimbach
2004-11-16 16:11 ` Fco. J. Ballesteros
2004-11-15 19:28   ` Steve Simon
2004-11-16 16:17   ` andrey mirtchovski
2004-11-16 17:07     ` matt
2004-11-16 17:15     ` rog
2004-11-17  0:15       ` Charles Forsyth
2004-11-17  1:08         ` Kenji Okamoto
2004-11-17  8:58           ` Richard Miller
2004-11-17 15:01             ` Ronald G. Minnich
2004-11-16 21:14     ` Jack Johnson
2004-11-16 16:37 ` Matthias Teege
2004-11-17 20:53 ` Vester Thacker
2004-11-22 20:16   ` Dan Cross

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=6e35c06204111719543e8d6657@mail.gmail.com \
    --to=knapjack@gmail.com \
    --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).