linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: berk walker <berk@panix.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: [OT] best tape backup system?
Date: Sat, 26 Feb 2005 18:09:56 -0500	[thread overview]
Message-ID: <422101C4.20901@panix.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0502261730450.14465-100000@coffee.psychology.mcmaster.ca>

And worse yet, you have to run them to the end and then rewind them if 
you are going to keep the data for long [the magnetic fields affect 
layers near them]. An array of RAID1 disks, which sleep deeply [off] 
between uses would probably be affordable, and last MUCH longer.

Just my 2 cents worth-
ya, well, that's what you get for 2 cents.
b-

Mark Hahn wrote:

>>Not sure if it is important to many people, but tapes take a lot less
>>electricity than online disks.
>>    
>>
>
>do you really care?  an active disk is about 15W, inactive 5W
>and asleep nearly zero.  even assuming idle-but-spinning, 
>I make that as about $2/year.
>
>tapes are wonderful in every way except one: they're finicky
>and difficult to care for properly.  for instance, do you have 
>a humidity and temperature-controlled place to store them?
>and have you actually logged the temp/hum for that to see 
>whether, for instance, it gets warm on weekends?
>
>if I were forced to use tapes, I would insist on making 2+ copies
>of everything.  note that this clearly hurt's tape's competitiveness
>WRT price, size, bandwidth, etc.
>
>I don't see any new tape installations that are not driven by 
>secondary factors such as big piles of old data already on tape,
>or someone wanting to physically move the media into a vault.
>
>(on that topic, I don't buy the idea that tape's less vulnerable 
>to hacking, either.  just because your backup is on disk doesn't
>mean that it's online or accessible.  similarly, just because 
>your tape is in a separate cabinet doesn't mean that a sufficiently
>motivated badguy could not get the tape put into some drive...)
>
>regards, mark hahn.
>(buying many TB of disk this year and no tape)
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>.
>
>  
>


  reply	other threads:[~2005-02-26 23:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 10:28 [OT] best tape backup system? Louis-David Mitterrand
2005-02-22 11:05 ` Lajber Zoltan
2005-02-22 15:41 ` Gordon Henderson
2005-02-22 16:50   ` Guy
2005-02-22 17:40     ` Gordon Henderson
2005-02-22 21:39       ` Guy
2005-02-22 21:52     ` Michael Tokarev
2005-02-23  1:26       ` Guy
2005-02-23 18:28         ` Michael Tokarev
2005-02-23 19:46           ` Guy
2005-02-22 22:07 ` Jon Lewis
2005-02-22 22:13   ` Alvin Oga
2005-02-22 22:36     ` Jon Lewis
2005-02-22 22:48       ` David Dougall
2005-02-26 22:40         ` Mark Hahn
2005-02-26 23:09           ` berk walker [this message]
2005-02-22 23:00       ` Alvin Oga

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=422101C4.20901@panix.com \
    --to=berk@panix.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-raid@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).