From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: [OT] If RAID's not backup... what do you use?
Date: Fri, 21 Nov 2008 09:28:05 +0000 [thread overview]
Message-ID: <49267F25.4080806@anonymous.org.uk> (raw)
I currently have a 3x1TB RAID-5 array. It contains backups of my other
machines, taken with rsync. It's my central filestore, rsync'ed locally
so I have previous editions. It also holds my media archive, and in
particular my music collection that I really don't want to have to rip
again. So while part of it is backup for other systems, part of it needs
backed up. I'd like some means of coping with fire or theft of the
server. I want something with some room to expand, which can do the
whole job unattended. So what would the storage professionals here
recommend? Tape autoloaders big enough to cope with >2TB seem stunningly
expensive to me; even the tapes are as expensive per GB as hard drives...
Thanks in advance,
Cheers,
John.
next reply other threads:[~2008-11-21 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 9:28 John Robinson [this message]
2008-11-21 9:33 ` [OT] If RAID's not backup... what do you use? Justin Piszcz
2008-11-21 11:56 ` Wolfgang Denk
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=49267F25.4080806@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.