From: Jeff Anderson-Lee <jonah@eecs.berkeley.edu>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: petabyte class archival filestore wanted/proposed
Date: Thu, 22 Jun 2006 11:58:48 -0700 [thread overview]
Message-ID: <449AE868.2040500@eecs.berkeley.edu> (raw)
In-Reply-To: <OF996C9BE3.39146C6D-ON88257195.0062966F-88257195.0064AF15@us.ibm.com>
Bryan Henderson wrote:
>> 1) Tapeless: maintain multiple copies on disk (minimize
>>backup/restore lag)
>>
>>
>Can you really call it archival if you're willing to pay 5 times as much
>for quick access? Maybe you need a different word. Archive means large
>quantities of data with very low access frequency. And sometimes, in the
>current legal climate, with very low chance of destruction.
>
>You word this as if the only potential use of tape is backup of disk-based
>data, but it's also pretty useful as the primary copy of archival data.
>
>
I know some people swear by them, but our experience with tertiary (tape
and optical) storge systems has never been positive. (We have tried
several over the years, from several vendors.) Leave it at that, and
let's just say we want to explore new territory.
There is also an argument that the cost of tape and disk is slowly
converging/crossing. Some disagree, we find it an interesting point.
For many users, the cost of archival storage is often dominated by
non-hardware costs. Our internal departmental recharge rates for (tape)
backed-up storage are on the order of $5/month to $10/month per GIGABYTE
of storage. That's $60/GB/year to $120/GB/year. Very little of that
cost is hardware. Considering that a GB of disk now costs $1 to $2 for
commodity disks, I can afford to keep several copies of my data online
for quick access when I do want it, especially when it is mostly
archival and doesn't change that often (almost never).
Jeff Anderson-Lee
Petabyte Storage Infrastructure Project
University of California Berkeley
next prev parent reply other threads:[~2006-06-22 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 16:43 petabyte class archival filestore wanted/proposed Jeff Anderson-Lee
2006-06-22 18:19 ` Bryan Henderson
2006-06-22 18:58 ` Jeff Anderson-Lee [this message]
2006-06-23 0:57 ` Bryan Henderson
2006-06-22 19:53 ` Jeff Garzik
2006-06-22 20:29 ` Jeff Anderson-Lee
2006-06-23 4:26 ` Andreas Dilger
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=449AE868.2040500@eecs.berkeley.edu \
--to=jonah@eecs.berkeley.edu \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).