From: Paul Jackson <pj@sgi.com>
To: davidsen@tmr.com (bill davidsen)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove obsolete onstream support from ide-tape in 2.6.3-rc3
Date: Tue, 17 Feb 2004 02:13:15 -0800 [thread overview]
Message-ID: <20040217021315.14ca7a9a.pj@sgi.com> (raw)
In-Reply-To: <c0rmfa$453$1@gatekeeper.tmr.com>
> but can't read anything more than about a decade old.
Yes. One has to abandon the idea that offline storage is archival.
It's just for disaster recovery. Archive online. Backup to removable
disk, or, if you're Linus, everyone else's computer ;).
I keep everything I've ever done that I might ever want to see again
(DOS, Warp, Win, Irix, Linux, ...) on one disk, my current disk. It
gets copied over, and appended to.
If it's not on that disk or its backups, it no longer exists.
Backups, now on removable IDE drives, only have to last a year or so, in
case I didn't realize something was missing for a while.
I'm working on a disk-to-disk backup program that is a radical departure
from existing backups. It maintains a single version controlled ascii
line oriented master list file, and plain copies of the backed up files,
exactly one such copy per unique md5sum. It handles 50 Gbytes in 30
minutes (300+ files per second). 186 lines of Python. No tar, no cpio,
no compression, no binary file formats, no streaming media; trivial and
robust.
The economics of backup and archiving have changed, with the continuing
rapid decline in dollars/bytes of online storage.
New strategies are called for.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
prev parent reply other threads:[~2004-02-17 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 22:11 [PATCH] remove obsolete onstream support from ide-tape in 2.6.3-rc3 Willem Riede
2004-02-15 23:32 ` Paul Jackson
2004-02-15 23:47 ` Willem Riede
2004-02-16 1:08 ` Paul Jackson
2004-02-17 0:15 ` bill davidsen
2004-02-17 10:13 ` Paul Jackson [this message]
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=20040217021315.14ca7a9a.pj@sgi.com \
--to=pj@sgi.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@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