Slashdot Mirror


Long-Term Storage of Moderately Large Datasets?

hawkeyeMI writes "I have a small scientific services company, and we end up generating fairly large datasets (2-3 TB) for each customer. We don't have to ship all of that, but we do need to keep some compressed archives. The best I can come up with right now is to buy some large hard drives, use software RAID in linux to make a RAID5 set out of them, and store them in a safe deposit box. I feel like there must be a better way for a small business, but despite some research into Blu-ray, I've not been able to find a good, cost-effective alternative. A tape library would be impractical at the present time. What do you recommend?"

34 of 411 comments (clear)

  1. Exactly what you're doing by rwa2 · · Score: 4, Informative

    I don't think you can beat a bunch of conventional hard disks in a RAID5 for both cost-per-TB and backup/restore performance, not to mention medium-term data integrity. Might be able to make hooking up the drives more convenient with an eSATA mult-bay enclosure, but those are kinda expensive. But I bet your backup box already has some sort of hot-swap on it already, like: http://www.amazon.com/Thermaltake-BlacX-eSATA-Docking-Station/dp/B001A4HAFS

    I assume you already compress your data, since scientific datasets tend to compress well. You might consider compressing to squashfs, since it will let you do transparent decompression later on so you can skip the restore step if you just need a handful of files.

    1. Re:Exactly what you're doing by forgottenusername · · Score: 5, Interesting

      I don't think it's a great solution. You're storing relatively fragile hard drives in a raid5 configuration in a lock box? It's not like you can tell if one of the drives goes bad and needs to be replaced when it's sitting in a box. You'd have to regularly pull the data sets out, fire them up and make sure everything is still functional.

      I'd at least want to do 2 complete sets of mirrored drives.

      Tape storage does store better.

      Depending on how important the data is, I might do something like a local mirrored drive set in storage and an online copy at something like rsync.net - stay away from s3, it's not designed to protect data, despite what AWS fans may say.

    2. Re:Exactly what you're doing by hardburn · · Score: 4, Insightful

      That's why you hot-swap them. You treat them just like tapes. In fact, once you start doing that, you realize that RAID mirroring isn't helping you any (striping is another matter).

      The best way to backup a big hard drive these days is with another big hard drive.

      --
      Not a typewriter
    3. Re:Exactly what you're doing by TheMeld · · Score: 3, Informative

      The other thing to do if you want longish term reliability is to add redundancy to whatever you're storing with a tool like par2, http://www.par2.net/ and http://www.quickpar.org.uk/ are your friend.

      Raid5 will help you if you lose a whole drive (e.g. siezes up from sitting still for a long time), the par2 data will both allow you to verify that the data hasn't been corrupted, and if it is (e.g. a couple sectors go bad), it will let you recover the data.

      --
      -Cheetah
    4. Re:Exactly what you're doing by rwa2 · · Score: 4, Informative

      Yeah, keeping those drives in a huge online storage array is probably better. Then they can mirror them across multiple sites.

      Here's a compelling petabyte online RAID system for cheap:

      http://blog.backblaze.com/2009/09/01/petabytes-on-a-budget-how-to-build-cheap-cloud-storage/

    5. Re:Exactly what you're doing by TrippTDF · · Score: 4, Funny

      your sig is incredibly apt for your post...

    6. Re:Exactly what you're doing by lgw · · Score: 4, Informative

      Tape is really best for archiving, to this day. A single LTO drive won't break the bank for a small business, and it will be reliable.

      3 Things to remember about tape backup:

      Encrypt your backups. This is becoming available in the tape drive itself, but many backup applications will also do it for you in software. Limits embarassment if a tape goes missing.

      Occasionally test restores. This is incredibly important - almost every unreadable tape in existance was unreadable when created. Any reasonable backup software will give you the ability to do this automatically (as part of the backup job). If practical, create a job that does a backup of everything, but verifies only some small volume. If you can read anything, chances are high that the whole tape is fine.

      Get those tapes offsite. A safe deposit box works for a tiny company, but someone like Iron Mountain works better and is less hassle. Store a copy of your encryption key in the same facility (but don't transport the tape and key together).

      --
      Socialism: a lie told by totalitarians and believed by fools.
    7. Re:Exactly what you're doing by Again · · Score: 4, Insightful

      (Or btrfs on a Linux distro)

      Are you honestly suggesting using an in-development filesystem for backup purposes?

    8. Re:Exactly what you're doing by Vellmont · · Score: 3, Insightful


      if it was medical records i'd be storing 5 copies in 5 geographically distinct locations, each with their own backup for the backup. i'd be checking the MD5's each day on all the backups to ensure they can be accessed when i need them

      I can about guarantee you that nobody stores medical records in this way. And realistically, why should they? 5 different locations is insane for just about any piece of data.

      Geeks tend to go overboard when it comes to data paranoia and worry too much about technology, but then forget about all the human problems that go on. Most data loss doesn't occur from some geographic catastrophe where a super volcano destroys half a continent. More often someone changes some critical path of the backup scheme and the whole she-bang comes crashing down. Super-redundant geographic co-location can't save you from one idiot that didn't understand changing one critical name silently took down the backup scheme.

      --
      AccountKiller
  2. bzip2 by Colin+Smith · · Score: 5, Funny

    And optar:

    http://ronja.twibright.com/optar/

    You know it makes sense.

    --
    Deleted
  3. Amazon AWS? by TSHTF · · Score: 4, Interesting

    It might not be the cheapest option, but with Amazon's AWS, you can snail mail them a copy of the drive with the data and they're store it in S3 storage buckets.

  4. Different manufacturers by idiot900 · · Score: 4, Insightful

    Hard drives are ridiculously cheap these days, especially for how much data you are storing. You may wish to consider buying drives from different manufacturers but of the same size to put in a single mirrored set. This way if there is a problem with a particular batch of drives it won't ruin everything.

  5. Tape is your friend by chill · · Score: 5, Informative

    LTO tape, properly stored, will outlast burned optical media and hard drives. Great stuff and designed specifically for what you're talking about.

    http://en.wikipedia.org/wiki/Linear_Tape-Open

    --
    Learning HOW to think is more important than learning WHAT to think.
    1. Re:Tape is your friend by cruff · · Score: 3, Informative

      I agree, when the tapes are stored in proper environmental conditions. You don't need a library, just use some stand alone tape drives. Also look at the claimed media lifetime and recovered bit error rate figures to see if you are choosing the right tape drive/media.

    2. Re:Tape is your friend by Saint+Aardvark · · Score: 5, Informative

      Couldn't agree more. A tape library (as in autochanger) might be out of your budget, but a simple tape drive wouldn't be too much -- say $5000 for an LTO4. Media is $50-$100 or so depending on where you shop. Seriously, you're not going to find a reasonable way of storing that much data anywhere else.

      BTW, if you're not a member of LOPSA, you may want to seriously consider it. Even if you're not a sysadmin, this is definitely a sysadmin-type question, and their mailing lists are second to none. It's an excellent resource.

    3. Re:Tape is your friend by mengel · · Score: 3, Insightful

      There's some code lurking in the amanda backup package I did a while back for "RAIT" (RAID with tape instead of disk) to make a stripe-set of tapes, if you need several tapes worth of data in one set, with redundancy.

      On the other hand, while LT04 tapes are about half the price ($40) of cheap 1TB disk drives ($80), the tape drives are ablout $2k apiece, so depending how many data sets you want to keep, and for how long, the disk drives may really be cheaper...

      --
      - "History shows again and again how nature points out the folly of men" -- Blue Oyster Cult, 'Godzilla'
  6. Amazon S3 by friedo · · Score: 3, Informative

    It can get a little pricey for huge datasets, but Amazon S3 now has an option where you can ship your data on a big set of disks directly to them, they will import everything into S3, and it will live there forever. The nice thing about S3 is unlike physical disks, it can grow essentially forever, and comes with retention and redundancy guarantees. And once your stuff is in S3, you can recycle the same disks to mail them more data.

  7. Go with Blu-ray by sabreofsd · · Score: 3, Interesting

    With the advent of 2TB drives, you could easily combine 3 of these with software RAID 5 as you suggested. Depending on how long you need to keep the data, recording them to dual-layer blu-ray disks might be a better solution. Ya, it's a lot of disks (you can buy 100GB discs now), but they'll last longer and you don't have to worry so much about mechanical failure or needing a certain OS when you want to restore them.

    --
    Sabre
    1. Re:Go with Blu-ray by eldepeche · · Score: 3, Insightful

      I thought burned optical discs started to degrade after a few years. Have they solved this problem?

  8. Drobo fan and user by Lvdata · · Score: 3, Interesting

    You might look at a www.drobo.com as a set of 4,5 and 8 drive enclosures. 1 TB disks gives you 3 TB usable space with a 2 drive failure tolerance. I have the older 4 bay drobo (2 for myself, and 2 at separate clients offices). It is much simpler to use, and will scale to your 2-3tb use and allow mismatched drives that normal raid will not use. Get a enclosure to start with, and then financing permitting, get a 2nd for Drobo redundancy. Not the fastest or cheapest, but reasonably good by both accounts, and simple to use.

    1. Re:Drobo fan and user by pavera · · Score: 3, Informative

      You misunderstood the post. He needs 2-3TB PER CLIENT, not 2-3TB total.

  9. Re:Exactly. by TooMuchToDo · · Score: 5, Informative

    Because Amazon can be *expensive* compared to doing it yourself ($$$ for data in, $$$ for data out, $$$ for monthly storage). But heh, what do I know. I just manage the storage for one of the LHC detectors (5PB spinning disk, 17PB tape). Amazon is good when you've got VC money or have no IT folks.

  10. I'd encrypt the data and... by Rivalz · · Score: 5, Funny

    Label it something like complete american idol blueray collection and upload it on p2p to piratebay. every couple years rename it to some other horrible popular tv series. It will be self sustaining form of storage with infinite number of redundant hosts.

  11. Use RAID6 not RAID5 by jbridges · · Score: 3, Insightful

    I would use RAID6 not RAID5, since 2 drive failures means data loss with RAID5, while it takes 3 drive failures to loose data on RAID6.

    Linux MDADM has supported RAID6 for years, it's stable.

    I would mix and match drives, not buying all the same model from one maker. One Samsung, One WD, One Hitachi, One Seagate.

    That gets you 4TB in 4 drives, and unlike a RAID1, any 2 drives can fail with no dataloss.

    You can further ensure no dataloss by making a second copy using different brand drives for each clone.

    Eight 2TB drives is around $1500. Not bad for a very safe 4TB backup.

  12. use a tape drive by Lehk228 · · Score: 3, Informative

    you make the assertion that a tape archive would be impractical, but really it is the most practical solution. the drive will set you back a couple thousand, but 800 gig tapes are only around 40 bucks each, and they are engineered for data storage unlike hard drives. this will only cost $160 per 3 gig dataset, or 200 if you use par2 files and an extra tape to make it recoverable in case a tape does fail.

    --
    Snowden and Manning are heroes.
  13. Re:Exactly. by Anonymous Coward · · Score: 5, Insightful

    Ok, yes, we see you know a lot about this.

    So what's your recommendation?

  14. Re:Exactly. by snikulin · · Score: 3, Funny

    Huh, don't you see has has Too Much to Do?

  15. Agree with the tape option..;. by klubar · · Score: 3, Informative

    Tape is probably your best option. You can buy at DAT-5 (or even a DAT-4) tape drive for not very much. The tapes cost about $10 to $30 each (depending on what tape option you choose). Make 3 copies of the data set, store one onsite, store another offsite in a secure/climate controlled facility and send the 3rd to the client. Buy a spare tape drive and use both to make writing across tapes easier. There is a wide variety of software to write to the tape; we use the aging Retrospect.

    The disk options is just way too complex; if anything, skip the RAID option and just store 2 copies. Putting the RAID sets back together and finding the RAID software will be nearly impossible in a couple of years. Use some standard formatting on the drives (FAT, NTFS, etc.) and you'll be good to go for the next 15 years.

  16. Never us DVDs as long term storage. by strangeattraction · · Score: 4, Interesting

    Repeat never use DVDs as long term storage. I have seen them go unreadable anywhere from 2-5 years. I have fired up disk drives 10 years later with no problems. They are cheap reliable and fast. Don't try and get fancy just compress and store data sets over multiple volumes. Don't use RAID.

  17. Re:GMail Drive by 0100010001010011 · · Score: 4, Interesting

    That's what ZFS is for.

    mount -t gmailfs /disk1 -o username=gmailuser,password=gmailpass
    mount -t gmailfs /disk2 -o username=gmailuser,password=gmailpass
    mount -t gmailfs /disk3 -o username=gmailuser,password=gmailpass
    mount -t gmailfs /disk4 -o username=gmailuser,password=gmailpass
    mount -t gmailfs /disk5 -o username=gmailuser,password=gmailpass

    zpool create gzfs raidz1 disk1 disk2 disk3 disk4 disk5

    Actually.... I think I just found my project for the evening. I mean it's already been done with 12 USB drives

  18. Depends on frequency of access by adosch · · Score: 4, Informative

    I work as a contractor for the USGS and the projects I've been involved with host, archive and provide means for customers to access all our different satellite data products. We've got a Long-term archive method for tons of data products (digitally and tangible) and I can honestly tell you the first thing that always comes up is: how often will the data need to be accessed?

    For the longest time (almost a decade) we used 3 big, STK tape silos for data archive and retrieval for custom orders. The problem behind that type of design is we used a archive in a completely wrong manner in the fact that we tried to use it as a archive and a quasi-online retrieval system into a caching filesystem. We had tape mount counts in the hundreds and thousands, constant mechanical tape issues because of the excessive use, ect. We actually decided to move it all to online storage using enterprise RAID (EMC Clarion) and moved to a small LTO-4 tape unit for almost permanent, maybe-once-in-a-great-while storage and the rest we leave completely on spinning disk and control the access to it via application layer network protocols as needed.

    IMHO, I really think it's going to depend on the access frequency of your data. If that custom needs their data once, and maybe never again in case they lose it, put it on tape. If it's a requirement they can get the data from you any time they want and you've got the hardware and administrative resources, power and bandwidth, put it some RAID.

  19. Re:Exactly. by TooMuchToDo · · Score: 4, Insightful
    Either MogileFS, Lustre, or possible Hadoop (depending on the type and size of the data). Any sort of distributed file system where multiple chunks, replicas, etc (3 is a good number, more is better if you have cheap disk and deduping at the filesystem level) are constantly available.

    Feel free to ask more questions.

  20. Re:Exactly. by TooMuchToDo · · Score: 3, Interesting

    Almost forgot to add. Never pay for expensive disk systems. Put the intelligence into your application instead. It'll scale faster and much cheaper. You also aren't locked into a technology (and instead, can enjoy the falling costs of storage, both spinning and SSD).

  21. Another Option / Definition issues by bruciferofbrm · · Score: 3, Interesting

    A problem I have here is the definition of 'long term'. To each of us it means something different.

    In my job I have to archive 1.6 terabytes of data per day, and keep it around for 45 days (which, BTW, is not my definition of LONG TERM). For this task I utilize Data Domain storage, which utilizes data deduplication techniques for massive compression.

    What you find is that at the block level your data may in fact be incredibly deduplicatable. In my case it very much the situation. I am currently storing 86 terabytes of rolling archives within 2.5 terabytes of physical disk space.

    The problem with any technology you use for 'long term' storage is the ability to read those archives later. Assuming the media doesn't self degrade inside of the time frame you call 'long term', you must have the tools to read that media again. If you use BluRay, then you must store a compatible drive with it. (Nothing says Sony will not change the standard in two years and make all current drives obsolete, so no one makes them any more). Tape is worse, in that in two major model revisions, drives wont be able to read your media because its density is to low for the new drive head technology. Hardware based disk raid has the issue that the controller the raid was built with needs to stay with that raid. Another controller from the same manufacture, with the same model number, but a different firmware revision may not be able to figure out the raid, and declare the drives empty. Software raid is a little easier to deal with as long as you keep a copy of the OS you used to create it with in the same box. But then, during your defined 'long term' period, will you still have access to a system you can even plug these drives into, or run the OS on?

    What you end up dealing with in reality is that as an archivist, you either ignore these facts, or you invest in a constant media / technology refresh and spend large amounts of time keeping your archives on the latest storage available.

    Of course, all this falls apart if your definition of 'long term' isn't as long as some will project. In my case, my archives roll over every 45 days. I could easily keep that data alive for years on a live piece of hardware with a service contract. If I do not trust that hardware enough, I can buy two and replicate between them. (which, actually I am, for disaster recovery purposes)

    With deduplication my (acknowledged) high initial investment quickly outweighs the cost of single purpose drives holding one copy, and wasting unused space. My purchase cost was less then $60k, but if I had to store all of that data in its raw form, my costs would be in the millions. However, if the data is not deduplicatable, then of course it is a moot point.

    Each answer has it flaws. You decide which risks are acceptable, plan your best to deal with obsolesce, and define your definition of 'long term'. You also have to be ready to change your solution, when the one you choose today, fails to be the right solution for your needs in 5 years.