Tape still beats SSDs and hard drives when it comes to price per byte
techradar.com
techradar.com
The 2019 meeting just happened and had a lot of good info about current use of tape, slides should be online in another couple weeks. (I presented there this year and work at the Internet Archive, though we do not currently use tape in our storage infrastructure.)
Why does it take so long?
When you ask that (particularly in places like HN), are you expecting someone to have a revelation and and not understand that taxes pay for government services? Like free is shorthand for "no cost at time of use" here.
The drives are also quite expensive and if you use them for backups, you need to keep one ready in case the other borks it but you need the tape's data.
Lastly you need specialized tools for access since most average tools will mishandle the tape.
What in the world does that first number mean?
My best guess is that it's some nonsense math based on the fact that the tape head contacts 32 tracks at once. So writing a full tape is 1 "full pass", which equals 208 "end to end passes" as the tape feeds back and forth, which equals 6656 """passes on any area""".
So a few minutes of latency in the worst case, yes, but certainly not hours of latency, unless you must drive a car to an off-site location, but that would be the same for a HDD or optical disc stored in another place.
The file index is actually a relational database table with a lot of metadata about the files, including: position in the tape collection as tape number + file number, name, path name, modification time, length, content hash (to identify duplicates) and a set of keywords and tags, to be able to search for a file even when the name is not known, or to be able to retrieve sets of files.
The files written on the tape are grouped in compressed archive files, but the database with metadata is about the files inside of those archive files.
Obviously, the file index itself is also backed up regularly.
It gets worse when you have to use more than one set because there is too much data to have full backup daily and you also need to index few incremental sets.
In my custom program & file database, I only use physical tape names, i.e. the names that I write on the labels of the cartridges. Either the program tells me what cartridge to load in the drive, or I inform it what cartridge I have loaded (e.g. for a new cartridge). I see no reason for a logical name. If I would ever copy a tape on another and I would discard the original tape, it would be trivial to substitute the name in the database.
Maybe for a large enterprise maintaining a comprehensive file database could be time consuming even in the best implementation, but I doubt it.
In my experience, keeping an up-to-date file database for about 120 TB of content that increases by about 10 to 20 GB per day still takes a negligible time.
While I have worked in a few large companies where a lot of data existed, in all small- and medium-sized companies (less than 100 computers) that I have seen there was less backup data than that (not counting things like standard disk images with the OS and with SW, which do not belong in periodic backups and which where shared, being identical for various classes of employees).
Realistically it's 3 minutes.
Gmail had an event with data loss in their early days and restoring from tapes took (from memory) many weeks, if not months.
The tapes have the fastest sequential transfer speed of any alternative, so the restoring duration should be better than from anything else, if the restoring software plans correctly the sequence of retrievals.
It is true that if the backup software is not clever, you could waste a lot of time to determine what you must restore and where is it. However, this has nothing to do with the tapes, the same can happen with backup on HDDs if the backup software is equally bad.
I am not sure what you mean by having lots of more tapes than reader, as that is the point of tape storage and the cause of it low cost per terabyte.
The only way that I could understand that phrase as a disadvantage for tapes is that when you would need to read as fast as possible e.g. 300 TB with one reader, that would need 10 days, but if the 300 TB were stored on 25 HDDs and you would also have 25 spare computers and some technicians that could open the computers and connect the HDDs inside them and you would also have an 100 Gb/s Ethernet network from those computers to the destination of those 300 TB, then yes, you could read the 300 TB 12 times faster that with a single tape reader.
However, such circumstances seem too unbelievable. For such a huge organization it would be more realistic to buy immediately e.g. 3 more readers to reduce the reading time from 10 days to 2.5 days.
On the other hand, if the 25 HDDs would have been located from the beginning inside a backup system, then that system would have had a price with at least 5 digits, far higher than the cost of a tape backup system, and unless it would have been connected by 100 Gb/s or at least 25 Gb/s Ethernet, its speed could not have been much higher than that of a single tape drive.
Also, why on earth would you need 25 spare computers for 25 drives??? 25 drives fit into a single 4U chassi. A single operation and everything is done.
Seeking a file on a harddrive is about 7ms. Seeking 25 drives is also about 7ms. But will be quite the operation for a tape system.
You don't just "buy three more readers", you are likely making use of tape robots and fitting them into your infrastructure probably isn't an afternoon of work. And the whole cost benefit of tapes greatly rely on the fact that you don't have to. Which is also why the latency skyrocket. You still want to perform your backups of course, maybe doubly so because of any unforeseen secondary effects that whatever caused the restore process might lead to - which will compete with precious time.
I'd love to use tape, but the cost is prohibitive and you really want to verify your backups so for home use it is quite the hassle. In my opinion. But if I stumble on a great deal, sure! It'll be fun.
I have already mentioned that with other words at the end of my reply and in that case you will not have a speed 25 times higher, but maybe at most 4 times higher than a single HDD, i.e. twice higher than a single tape drive.
Maybe I misunderstood, but the initial posting mentioned a restoring operation from tapes that was slow and my point was that using HDDs is unlikely to make it faster. For a restoring operation the duration will be dominated by sequential transfers, not by seeking, so tape drives would be faster than HDDs, unless you use ridiculous resources, like in my example with a computer per HDD and with a network fast enough to aggregate the data from all computers.
If we are talking about general-purpose data storage on tapes, then obviously, what is frequently accessed should be on SSDs, because the average seek time for a file stored on tape will be between 1 minute and 2 minutes.
I suppose that there might exist applications where there exists a quantity of data so large that it would be too expensive to be stored on SSDs and with worst case latency requirements so severe that it cannot be stored on tapes, so you have to use HDDs. However, in some 40 years of using all kinds of computer systems in many companies, I have never encountered such an application. Everything I have seen could be better handled by a combination of SSDs and tapes, without any HDDs. The only problem with tapes is the prohibitive cost of drives, which limits their use to data sizes of at least 50 to 100 TB, unless long term storage reliability is more important than the cost.
Hours comes into play when you have a queue of retrievals and many tapes....
Another important factor everybody seems to forget is that you don't want the tape to be your only backup. They are so slow to restore that you typically only use tape as last resort.
For my personal backups I calculated a bunch of regular 4TB drives, external USB 3.1 bay which takes 2 of them at once and an off-site storage (place where I can keep drives) to be best solution.
Is it possible to replace the RW head on a tape drive? I guess the manufacturers generally don't want this to be easily replaceable, so they can sell more drives...
These old MP tapes are like sandpaper to new drives.
That being said, this does apply within generation to a lesser extent as well.
But the tape storage requirements and danger of running into trouble with the reader (especially considering I could get a misaligned one when buying used, and if that one breaks => tough luck) convinced me this isn't a good choice. [edit] For the same money I can just get a bunch of additional disks, and use two for simple, redundant, offsite backups; and the remainders to swap out old disks in the NAS pre-fail.
Then you place the tape robots into a fireproofed room with exhaustive protection measurements (e.g. filling the whole room with CO2 or similar on fire alarm, having extra fireproofed doors which are comparable with bomb shelter doors etc.).
Where tape shines is for offsite copies, DR copies, or duplication for safe keeping of any kind, not backups.
Tape will work for backups, but you have to structure your working processes around tape (serial access) to the backed up data. If for you "backups" includes rapid access to an old version of a file you edited or deleted by mistake and pulling in data that's too old for you to want to keep on expensive disks so you can process it, tapes aren't a good option, for reasons of access time.
Most modern IT professionals would use NAS or SAN snapshotting to handle the first case above, where you did an oops and need a copy of the file as it was before that. A snapshot directory on a NAS usually gets implemented using a journaling file system or some other mechanism for maintaining a point in time view of the system, so you're not keeping another complete copy of your data, only journal entries listing what changed when.
For the second case where you have too much data to fit on your expensive SSDs and you might need to use some of it e.g. next week or next month, what you want isn't tape, it's a cheaper hard drive. IT types usually call this "near line storage". State of the art spinning hard drives are a good option, but if those are still too expensive you can go a couple generations of technology back and get lower price/TB. The problem you run in to doing this is that you need more physical space and hardware and power/cooling for the lower capacity drives.
Tape is great for when you want to keep data but may not need to access it ever or might need to access it months from now, and when you can accept a delay in access of a day or two. DR copies, offsite vaulting of data for legal purposes, logs from systems you want to keep in case you ever need to check back on what happened 5 years ago, bulk data from experiments that may never be accessed again but which could be critical for someone if it's needed (and may therefore turn out to be extremely valuable)... those are the scenarios for tape, and the price per TB stored is lower than anything else.
The company where I work off sites data for long term storage regularly, including a copy of our main ERP database. We meet legal compliance requirements the cheap way by copying stuff to a tape we can access and paying someone to store it for us. Backups of production systems are done to disk, to a NAS or SAN block storage device that is then copied to tape if needed.
Edit: Forgot to mention the ERP databases' size... it's in the Petabyte range, it runs the entire company. If we tried to transmit it to a cloud backup provider, without spending a giant amount of money on a high speed internet connection we'd never complete a daily backup before it was time for the next one. On top of that, if we need 2 copies of it the storage price gets very high very fast - cloud storage is very convenient, but costs more than even local spinning disk. Tapes,on the other hand have a small incremental cost if we already have the drives and robot, and we can make as many copies as we like by paying only for the tapes and the time.
https://www.ecma-international.org/publications/standards/Ec...
Also look at the floppy imagers people have made, that operate at the magnetic flux level.
Try telling that to IKARI+TALENT, Legend, Skid Row, PaRaDoX and all the other cracking groups from Commodore64, Amiga, ATARI ST, PlayStations, Nintendos, groups which competed on who is going to one-file a program or convert a secret disk coding format to a regular filesystem, with all the protections disabled and the programs bug and NTSC+PAL fixed while they were at it...
It doesn't have to be slow, sometimes it can be quick, but the precondition is that it takes the most talented engineers in the field to do it...
So, either we have gross incompetence across the entire information technology industry in general if it's impossible or slow, or the people disassembling custom filesystems and protections, bug fixing binaries and adding custom speed-loaders in record time are from another planet. Which one is it?
"cats are furry. Your argument is invalid."
Now, is "Hacker News" supposed to be where the information technology elite gathers, or is that a gross misnomer these days?
It's also fine not to know, but your comment assumes we know who or what, for example, "allegory", "database", "cats" and "misnomer" are. My point is that every discussion assumes some knowledge, and if you lack it you can just look it up, or ask, without making allegories about cats and databases and huffing and puffing about information technology elites.
Sorry, I'm still not sure how knowing the LTO spec would be helpful.
You are basically asking for the "Layer 1" documentation of how the tape head write to the tape media? Given that you can only access the media via a drive, wouldn't it be sufficient to simply know the SCSI commands (T-10 SSC-x) to send? You'd then have to know the file format of the backup software (e.g., tar).
If you do care about the data on any given medium a few years from now, you copy it then to a current medium. And so on.
This works fine as long new media are cheap, easily available and higher density than the old. As has been the last sixty years. If this progress ever halts or reverses (due to some man-made or natural disaster, including a major economical recession), we're screwed.
Not to mention the closed format causes reduced competition in making better or cheaper devices, which is another downside.
What a miserable website.
Give it a try :)
Generally, you can add outline.com before any news or blog domain, and you get a reader view to share.
Their advantages to me is obvious: its inexpensive price and great longterm reliability beats any alternative choices: hard drives, optical drives, or solid-state drives, and sometimes cloud. Also, it's cool to put my "tape archive" (.tar) files on a real tape! But I found for personal uses, tapes aren't cost-effective, the entry-cost and initial investment of the tape drive is extremely high, it's all enterprise-grade SCSI or SAN. Unless you already have tens of terabytes of data (video studio?), buying a tape drive is unjustified. HDDs are still sometimes the only cost-effective choice for personal use.
Now I mainly use HDDs for large backups (> 300 GiB), multiple Blu-ray disks for medium-size backups (< 100 GiB), and use cloud for the smallest archives. I don't know if Amazon's "mail your drive to the cloud" service is available at my location, but it's also an attractive solution.
I'd like to hear about your experience.
* https://www.backblaze.com/b2/solutions/datatransfer/fireball...
[1] - https://www.fool.com/investing/2016/10/03/att-drops-its-cont...
Where did you get the gear?
How cost-effective is the overall setup compared to spinning rust?
How is driver support in popular operating systems?
Is there more you'd recommend taking into consideration or learning before jumping in? Especially beyond the obvious realities of extremely high latency, of course ;)
I never ended up using it personally, but when I was considering it, used gear on eBay was top of the list.
> How cost-effective is the overall setup compared to spinning rust?
For personal use, it is not even remotely cost-effective unless you are a data hoarder. The cost of the drive is simply too high. Also keep in mind that the drive can become damaged or need servicing.
It only makes sense if you are dealing with e.g. large quantities of video. The article cites a minimum 140TB where tape becomes cheaper but this involves some dubious decision-making.
> How is driver support in popular operating systems?
I have only ever used tape with Linux + custom software so I can’t speak of software support in general.
> Is there more you'd recommend taking into consideration or learning before jumping in? Especially beyond the obvious realities of extremely high latency, of course ;)
The obvious reality to me here is that it just doesn’t make sense unless you’re in spitting distance of a petabyte. The only thing I can imagine someone doing personally is video, and it would have to be a lot of video like some kind of long-running documentary project that you are producing in your spare time.
The other factor is to be more paranoid about mixing tape generations than the vendors suggest. Ignore the specs and stick to same-generation media and drives.
Efficiently writing to a tape means filling e.g. a 20 MB/s write channel for LTO-6, or 750 MB/s for LTO-8. Can you sustain 750 MB/s? It’s not so easy in practice. You throw away tape capacity if you get buffer underruns.
The drive doesn't pause while the buffer fills again? Considering the price of the drives, I find it very surprising that they don't do that.
The drive does stop, and it runs at different speeds depending on how fast you are feeding it data. However, this process wastes tape capacity as you switch speeds.
Do 10% of a tape at a time, buffered on a $200-$300 NVMe SSD?
It's cheaper to run the tape slower (you can adjust it so that it is very close to what you can sustainably deliver)
Not meaningfully, unless there's something ridiculous about the format I'm unaware of. A full tape write covers 160-200 linear kilometers. Stopping 10 times, which is once per hour, is barely anything. I haven't found anything listing the exact size of gaps, but I did find a post from someone having thousands of buffer underruns that was only losing half a second of capacity per underrun.
This means that each 50 GB file is written at 3 Gb/s, the maximum tape speed, but after each 50 GB the tape is stopped then restarted. So I write on each tape about 120 files with an aggregate size of up to 45 905 860 blocks of 131 072 bytes each. That is more than the 6.0 TB advertised for the tapes, so I do not waste any measurable tape capacity. The 50 GB file size is chosen because it fits inside the 64 GB RAM of the computer with the tape drive and certain algorithms that I am using to process the tape files (lrzip & par2, for compression & redundancy) are faster when the entire file fits in the RAM.
Since I don't have enough karma to write another comment anonymously:
Restoring from backups is a last resort for very important files deleted more than a few days ago (beyond what hourly/daily snapshots contain) or for business continuity (BCP) / disaster recovery (DR) of an entire system that cannot be recovered via automated configuration management rebuild. Snapshots to nearline storage reduce RTO for most common use-cases, and most users and systems don't generate much churn of data in a day. For recovery of important files, sending a courier out to retrieve a backup tape set from the vaulting provider implies the RTO would accept in a matter of several hours. An RTO of under an hour would imply backups would need to be stored on nearline media (commodity spinning rust) or at a backup cloud vendor like AWS Glacier or Tarsnap, which is more expensive than tape.
The deciding factor of how much to rationally spend on DR/BCP solutions follows from a Business Impact Analysis (BIA) to quantify the loss of a service over a certain time, which drives RTO and RPO goals. (A common factoid of DR/BCP is "about half of businesses who lose their data go out of business within six months.")
RTO - Recovery Time Objective - desire/need to recover within a certain time window
RPO - Recovery Point Objective - how close to the original is the recovery
I have an old Quantum DLT S4 drive and something like 18 tapes. Each tape is 800GB uncompressed and I get about 1.8x compression on average. It's an external unit connected via SCSI ultra 320. The ultra 320 SCSI card is something I picked up from ebay for like $20. The drive and tapes I got from a former consulting client who was going to trash it.
It was the last of the DLT line and is similar to LTO4. Get an LTO5 if possible; it has some cool features like partitions.
I only store my most critical stuff on tapes. Each weekend I do a tape swap and take the old tape to work on Monday and bring the oldest one back. I keep the tapes at work in case my house burns down or something (I lived through two house fires as a kid so I'm super neurotic about it, don't ask). The tapes are encrypted so nobody can recover from them if they get one. If my house did burn down I'd have to somehow procure another tape drive, but that would be the least of my problems.
I just use a custom tar script to do it. I tried both Bacula and Amanda in the past but they were too complicated or had other issues. My own tar script did what I wanted.
> How cost-effective is the overall setup compared to spinning rust?
Since I got most of it for free and I already had experience with tape, it was pretty good. I've had it since 2008 so it's over ten years old and still going. I also have some UBS3 backup disks that I use for daily backups. In all this time, only one tape has died and I do a full validation of the previous backups every time I bring a tape back and re-use it.
For new installs, go with some USB3 disks from Seagate or WD -- both are great, I have both. Avoid Toshiba due to some weaknesses in handling bumps and vibration during runtime due to firmware (Toshiba internal drives are great though) -- Don't ask me how I know this. Seal them into some kind of fire-proof/flood-proof safe and store somewhere that a fire/flood won't destroy it.
> How is driver support in popular operating systems?
I'm all linux. It works. All that matters is the SCSI card being supported. Make sure NOT to get a RAID card, regular SCSI only. The RAID cards often won't work with tape drives because the firmware is made for RAID drives, not tape.
> Is there more you'd recommend taking into consideration or learning before jumping in? Especially beyond the obvious realities of extremely high latency, of course ;)
So the only real advantage for me using tapes is that I got most of it for free, the tapes are more portable and lighter than a USB hard drive for carrying around. Almost everything else is a negative compared to USB hard drives.
I use some UBS3 hard drives for daily backups via an rsync --link-dest script that de-duplicates everything and that works great. For $100 you can get a 4-6GB USB hard drive from WD or Seagate and for my important stuff, that works fine.
I'm about to fill up my older 5GB drive -- it's down to about 200GB free space left. I already have a new 6TB drive I brought recently and when it gets down a little lower, I'll just replace it, do full backups, and put the old drive into storage for permanent archival.
Data backups is a full occupational specialty, like being a DBA, network engineer, security, or web monkey. I did TSM for awhile. There's a ton of issues in the hardware, strategy, security, performance, and more.
Do yourself a favor and just set up something simple that JUST WORKS and don't fuck with it too much.
Do a practice recovery once and that'll teach you how good your setup is and improve.
We ( work ) have a massive pile of DLT, mainly S4's...these were written 2005 to 2009 ish and they still restore just great. I mean, i wish they wouldn't as i'd love to be shot of them but they are too reliable.
The casual observer won't understand the difference between "ability to restore" and "doing backups", but it matters when the building burns down.
node_modules is shit anyway, and shouldn't be duplicated for every single project.
I have yet to find a good solution. My phone is crippled by the library and none of the Macs like it much either. I’d guess I was at 600gb.
I'm trying to use icloud photos, because then I have them where they belong on my iPhone, but I just don't like the way it works. It's slow on my mac, but it's nice to have thumbnails locally, and originals available when needed. Althought that also doesn't work nicely when dragging. It's cool that photos groups things on event, but for me, I like to have my "camera roll", and manually make albums. That's possible, but it's ust easier to drag files around. Also, I'm looking for a solution to 'archive' photos (hide them, because I took 10 pictures of 1 thing).
There was a time I wanted to write an app/service for this. I might still do that if there's enough demand.
I also haven't figured out how to archive some video material. Recently I started shooting small clips, with the intention to make small 5 minute videos of my trips. As I don't want to delete the original material, I also need a place to store them, but I don't want to "browse" them.
The drives are bloody expensive. Mine was around $5k.
LTO8 tapes are still hard to come by even though the patent dispute is settled. This should change soon.
The software to archive to tape is clunky and frustrating but it works. I use something free that integrates with Finder on Mac. I'm away from my office so dont remember what it's called.
The main benefit is that the tapes last for half a century and are very cheap per TB once you have made the initial investment in the drive. Very good for long term archival of films and source footage which is what I use it for.
When you do a lot of those, drive price isn’t all that expensive. My major gripe with it is that you couldn’t hook it up to a USB3. Rare ones had thunderbolt, but most were that bloody external SAS thing. Not really all that great when you don’t have those controllers around. Beats the purpose of external drives.
https://magstor.com/collections/magstor-thunderbolt-3-tape-d...
The tape cost is about 10 EUR per terabyte. Previously I was using HDDs for archiving. I have not followed closely the evolution of the HDD price, but looking now on Amazon I see about 30 EUR per terabyte.
I have a data archive of about 120 TB, but I am paranoid because of past data losses due to defective HDDs/CDs, so I store 3 copies of each tape (in different places).
That means that by using tape instead of HDDs, I have already saved 20 * 360 - 3000 = 4200 EUR.
Someone who would store just 2 copies of each tape (the minimum rational value), would need to have a data archive of at least 75 TB to recover the initial cost.
Nevertheless saving money is not everything, you also gain peace-of-mind because the chances of the tape becoming defective just from storing are negligible compared to a HDD, which if not used for a very long time might never start spinning again.
With tapes you must transfer the data only when you can no longer buy drives that would read them. With HDDs you should better replace them before their warranty expires, as I have seen too many that died immediately after that.
The tapes work OK both in Linux and in FreeBSD, but the FreeBSD utilities are more convenient, so I have connected the tape drive to a FreeBSD server and I transfer the data to be archived through 10 Gb/s Ethernet, which is faster than the 6 Gb/s SAS, so it is not a bottleneck. The writing speed of LTO-7 is 3 Gb/s, so that is the bottleneck anyway, not the interfaces.
That speed is much faster than of any HDD of up to 8 TB that I have ever used, but I have not checked the latest HDD models to see if they have improved their speed to levels comparable to tapes.
Using tape is very simple and retrieving any file (I have a tape index on my SSDs) takes at most 3 minutes, including the time to manually start the drive and inserting a tape in the drive. The maximum seek time is about 2 minutes. When I had a HDD archive, there was still the same time for manually selecting a HDD and inserting it in the HDD rack. For retrieving very large files, the tape can even be faster, due to the faster sequential speed.
The conclusion is that if you have data of at least several tens of terabytes and/or if you value that data enough to want to avoid any chance of losing it, than magnetic tape remains the best solution for now.
I use self-system engineered (read: self OS packaged) Bacula software for backups with a custom developed shell program which interfaces with Oracle RMAN to do backups.
I use Solaris 10 on sparc, which also goes for pennies on the dollar nowadays since there are few of us left who understand how to run it and even fewer who understand how to squeeze the most out of that hardware + software combination.
The tape library shows up as character and block files under /dev/rmt/ and the robotic arm with the barcode scanner under /dev/changer/, nothing special or fancy about it. There is another piece of freeware I compiled and packaged (whose name I forgot) which controls the robot arm and the scanner, also by issuing standard SCSI commands to /dev/changer/ files, nothing fancy or special about it. The tape library has enough capacity for full backups with three month retention policy, so the only thing I have to do is replace a worn out tape cartridge roughly once in three years. Backups are daily. The entire solution ran me around $800 (server + differential SCSI controller + tape library) and the tapes ran me $500, over the span of 12 years.
Pre-tape, I used disks, rotated them and kept them in a safe. Burned optical discs of my most important stuff. I had two experiences that caused me to change: I had a failure and went to do a recovery and in either haste or anxiety (I put this on me, I should have paused and took more time but I was rushing) I knocked the most recent drive off my desk and effectively killed it. The other was a bit more subtle (oddly, I have only had 3 backup recovery situations and I messed up 2 of them) but my “backup” was rsync to disk on cron and a backup started during restore and began to “remove” my good backup because the master didn’t have that restored yet. There are a lot of lessons in there, most significantly, “backup” is a different thing than live access to data, you want it versioned and somewhat fixed. Rsync isnt it. You don’t want to accidentally delete your backup. Tape switches your mindset on that stuff. I’m not going to pretend it’s cost effective for my needs (although I have a lot of hd+ video of my kids) but it’s durable, it’s purpose built and cold storage can’t really be hacked. There’s no monthly fees, no risk of a cloud provider sunsetting my tier of service, and 25T of tape is like $250. Drive MTBF numbers are big enough to be abstract and yet you will likely encounter it at some point, tape has these practical numbers that are ultra conservative and come from decades of experience; you sort of keep it in mind when you’ve used a tape a dozen times or so. That being said, when the drive flakes, I’m in for an expensive upgrade/replacement and when I do upgrade, I should copy my tapes to new ones with the new format which will take time and money. With SMR, it’s almost like discs are taking on tape like qualities and it’s not hard to find stories about people getting crap performance on their new disks. It’s not sexy but I feel very confident that I’ll be able to get my data if I need it. It’s really easy to store a tape in your safe deposit box or at your parents house too, they won’t accidentally kill it by knocking it off a shelf.
I’ve only ever read bad things about mixing generations despite the fact that the drives are capable of this (eg LTO5 tape in LTO6/7 drives) though I’ve not done this personally - but I wouldn’t recommend doing so based on this. Don’t be tempted to buy really old generations as if you ever need to restore in a disaster where you only have the tapes, you then have the nightmare of sourcing a new old drive too which by that point might be a lot harder.
You’ll want to think carefully about software setup. You’re probably going to wind up using some form of custom scripts unless you can put in the time to set up bacula properly and are sure it works for you (bare metal restore can be a tricky aspect of any system to verify it works properly). If you script your own then make sure you also understand the drawbacks of tar. tar as a tool is highly compatible which is good but is poor at recording incremental backups (there are some custom extensions which gnu tar has but this reduces compatibility) if you want to go with a more complex schedule than full backup every time. Tar also makes it difficult to seek to just the part of the archive that you need to get a single file. Again there are gnu extensions for this but this isn’t the best solution. Finally, tar then gzip means if your gzip stream gets corrupted then you might lose quite a bit of the tar archive so it’s not very resilient. You could rely on the drive compression but you might also consider other solutions, especially ones which also include checksumming. Consider either scripting around these or better what other tools could take its place (eg I have used dar in some of my setup as it handles this better but then you need to think about keeping a working binary around which can unpack your archives - I put a static compiled binary in my archive sets just in case).
Finally if you go down the tape route then consider strongly spooling your stream which will be written out to tape onto disk first, to give yourself maximum chance of getting the more consistent throughput onto tape which has benefits in terms of tape reliability (and may indeed wind up being quicker overall). That also allows you to easily write multiple copies of the same tape if you intend to send one or more offsite and keep one locally.
Where this setup works well for me is that when you start wanting many copies of your backups (offsite, multiple point in time full backups etc) then the cost effectiveness becomes a lot better than the equivalent with disk. I also trust tape to survive longer term on a shelf than disk.
Also keep in mind that capacity and bandwidth often assume 2.5x compression of pure text, which doesn't seem like a common scenario.
The article compares SSDs to tape is silly, access times are in the minutes when a robot is involved, and many minutes of you are swapping trays. Why compare to SSDs with that can to 50k IOPs and up?
Say a cloud vendor needs a bunch of HDD for a database workload with high IOPs. Using modern disks (4+ TiB) this leaves a lot of stranded disk storage that can only be used for low IOPs workloads.
Archive storage uniquely meets the criteria of lots of storage, yet low IOPs.
Disclaimer work for Google but have no knowledge of how AWS glacier works.
The telco equivalent was ISDN, where a single linecard with two sub-rate ports might be sold to a bank, and a domestic user. The bank could (and would) demand card reset 24/7 to restore service to their ATM, the domestic user simply lost carrier, and game state.
Though a comment on that page mentions this HN comment claiming custom low-speed HDDs: https://news.ycombinator.com/item?id=4416065
This doesn't mean that they seem simply superior, though. I imagine optical discs have way better seek times, for example, even if read/write speeds are better with tape.
I had this problem - store and forget, long time, as in decades. Tried a lot of stuff and: Personal conclusion - offline backup sucks, regardless of medium. Tape, harddisks, zip drives - demagnetization of medium. CD, bluray - scratch and you're done. Thumb stick, SSD, non-volatile memory in general - needs a plug-in once in a while. So what I use is encrypted volumes and upload to cloud...and a dedicated SSD that I have on me at all times if I need offline access (which gets plugged in daily).
IME the problem of optical discs is that unless they're molded (ROM) they degrade over time.
When the Laboratoire National de Métrologie et d’Essais performed an extreme conditions accelerated aging test (90°C and 85% RH) they found the M-Disc to be no better than most quality DVD+R (<250h), with MPO's Gold and Northern Star's DataTresorDisc reaching 250h (but not 500) and Syylex's GlassMasterDisc surviving almost unscathed to 1000h.
Sadly it looks like Syylex is as dead as Millenniata, Inc (though it looks like Verbatim still sells m-discs).
It looks like someone took over the production of M-Disc (wiki: "The debt holders subsequently started a new company, Yours.co, to sell M-DISCs and related services."), not sure about Syylex. Syylex seems like the perfect solution (making discs in glass, the material that is routinely used in chemical labs due to it's inertness), but the problem always was that it cannot be burned at home...
Only if the other parameters are within certain bounds, otherwise your backup medium would be macro-scale physical engraving on a highly resistant substrate, at least some sort of stone, ideally a refractory or noble metal. Rhodium would probably be your ideal standard.
What do you mean by this? It is non-volatile after all.
The retention time depends on the storage conditions, especially on temperature & humidity. For ancient flash memories, with large cells and 1 bit per cell, the retention time can be of 10 years or even 20 years. After that the capacitor will discharge, because the insulation is not perfect.
For modern flash memories, with much smaller cells and wit 3 or even 4 bits per cell, the electrical charge variation that will lead to wrong bits is much less, so the retention time can vary from a few years for a new SSD stored at low temperature to a few months for a used SSD stored at a higher temperature. At a high enough temperature (not impossible to reach, e.g. when forgotten in sun light), the retention time can be reduced to days.
When a SSD is used, i.e. it is powered, the microcontroller inside it rewrites its cells from time to time to avoid losing data. If you store it without using it, after the guaranteed retention time you may lose data. Consumer SSDs and memory sticks are guaranteed for a retention time of 1 year, so you should not expect more than that.
That is good to know! Thanks for the explanation! Now I know to never use an SSD as backup o.O
It's unpleasant having to buy old drives to keep with your tape archives because you won't otherwise be able to read them any more.
Source: have done this at scale, have spent time scouring the second-hand market to cobble together early-generation LTO drives.
I think we had 4 cartridges of 7, then upgraded to a newer robot that had 8 cartridges of 11.
At the time I was pretty shocked, and asked around and apparently it wasn't a particularly unusual event. Fortunately we always kept a cartridge rotated out to a different room.
Similar with the drives, but the drives were fine.
Also sadly the great price/performance brand with great service (overland) got bought up by the radically more expensive larger company and all the prices doubled 8-(.
NAND flash can leak charge over time if not powered on which makes it unsuitable as an archival medium. Depending on P/E cycles each cell has undergone and the drive type (SLC/MLC/TLC/QLC) it can be from 3 months to 10 years.
Further, DVDs are effectively obsolete these days and MDisc's Blu-Rays have no scientific studies backing their claims to longevity compared to competitors like the DVDs did. One of their largest advantages relative to DVDs is completely gone in Blu-Rays as well: The inorganic dyes and recording layer (these are now standard for essentially all BD-Rs).
[0]: https://www.lne.fr/sites/default/files/inline-files/syylex-g... and full test and results in French: https://francearchives.fr/file/de7f8ea96ceb4ce38eb6d9278b3df...
"Good enough for Google, good enough for you"(a lie that neglects economies of scale that force Google to use tape). https://www.overlandstorage.com/blog/?p=323
Obviously, because the drives are extremely expensive, whoever needs no more than 20 or 30 TB of storage cannot afford tapes and must use a few HDDs. The best storage technology changes in time. 20 years ago I was using optical disks and 10 years ago I was using HDDs, but since I went back to tapes, like I was previously using 30 years ago, I have saved a lot of money and I have much less worries about the HDDs becoming defective.
Nevertheless, these HDDs are much more expensive than they look at the first glance. The real cost of archival storage is given by the price per TB and per warranty year, because after the warranty time you must replace the storage medium.
I have seen countless HDDs that have died just a few months after their warranty time expired.
So these drives with 2-year warranty cost $8.75 per TB and per year.
The warranty time of the tapes is 30 years, but in fact you must replace them much faster because you will no longer find tape drives able to read them.
For LTO tapes, you should expect to replace them after 6 to 10 years.
Even with only a 6 year lifetime, the price for tape would be $1.67 per TB per year, i.e. more than 5 times cheaper than those WD HDDs.
If you want to just have some backups against accidents, which you expect to erase after a few weeks, then those HDDs could be a good choice.
For archival purposes they are still much more expensive than tapes.
To reach only double price of tapes you must choose some super-ancient junk, e.g. 1 TB 3.5" HDDs, which are much slower than tapes and which require a huge size and weight for the same capacity as tapes.
12 TB HDDs have about the same volume as LTO-7 tapes (i.e. about the same volume as two 6 TB tapes), but they are much heavier. LTO-8 tapes have double capacity compared to LTO-7.
If you do care about warranty you can just keep them in the external usb casing and enjoy having an abundance of power supplies and USB 3 cables.
If it's 24/7 hot storage it also uses 50kWH per Year at 6W. That's also about 15EUR/Year minimum energy costs per drive.
Me feeling is, that all HDD manufacterers are extracting as as much value from the market as they get away with (meaning having more of a smell of informal price fixing, then of free market) while they still can, before they will be made osolete to solid state storage in 5 years latest.
Me feeling is that the competition in the tape market is also a bit rusty, $3000 for a fancier VCR, what a steal! ;-)
(Actually this problem is why I haven't owned a tape drive for a while.)
I'll get a small benchmark script for that done over lunch. Come back here later.
Is this a continuation from previous message ? Because multithreading mode of zstd doesn't impact its compression ratio. It's actually an interesting property of zstd : whatever the nb of threads used, the compression ratio remains the same (aka. reproducible).
Imagine a disk. It has two sides and a certain surface area, as well as a certain density (bits per square in/cm). A standard 3.5" HDD platter has a bit more than 4200mm^2 of surface area (having been unable to quickly find the dimensions of an HDD platter, I grabbed the dimensions of a floppy disk from the standard) per side, or a little less than 10000mm^2 per platter; I'm being deliberately rough with the numbers since all we need is an order of magnitude.
Imagine a tape. It's long and thin, and can be rolled up. An LTO-8 is 960m long and 12.65mm wide, for a total surface area of 12,144,000mm^2. Tape has a lower recording density than HDDs (LTO-8: ~20Kbit/mm * 6656 tracks, or ~128MB/mm^2 compared to ~1Tbit/in^2 = ~185MB/mm^2 for a HDD), but more than makes up for it with its length.
Also with inefficient tapes you end up spending many more tapes for inefficient incrementals, incredibly long seeks, and lack of efficient deduplication.
Then there's other nasty surprises like a relatively narrow temperature range for tapes and an improper alignment of the head can result in tapes you can read and write... but when the drive dies you can't read the tapes anywhere else.
Tapes still make sense above a certainly scale, but I think it's around 10PB before the real world costs of tapes, drives, robot, support agreements, extra capacity for inefficient incrementals/dedupe, etc.
The big win with tapes is it's much more feasible to rotate tapes offsite.
Tapes are also physically smaller, therfore their capacity per volume is better than for HDDs. Two LTO Ultrium catridges have about the same volume as a 3.5" HDDs, so you have 24 TB in the same space as a 14 TB HDD.
Moreover, the HDDs are much heavier. You can easily carry a suitcase with 20 tape cartridges, i.e. with 240 TB.
If you would carry a suitcase with 17 HDDs (238 TB), that would be around 14 kg (around 31 lbs). Possible but not at all comfortable.
Note: You can't reformat them this way. This is a permanent choice you make with a blank tape.
This was all donkeys years ago, so it is interesting to hear how things have changed.
Disappeared for no apparent reason about a decade or so ago.
How does storage tape even work? Is this literal tape in a cartridge much like tape in a cassette tape? I assume we’re not talking about data stored in 1s and 0s? Is this technically an analog medium!?
Going to do some googling now to quell my curiosity.
The article does seem targeted at consumers. I’m going to guess I’d need some expensive hardware to even use one of these $60 tape drives.
I am getting over 500MBps on my setup
Will you share more information about the specific details (i.e. hardware and configuration) for the set up you're running with?
is that always true? what if I have dozen's of pdf's which are similar and compressed (most pdfs are)? wouldn't de-duplication also reduce the size? I mean with millions/billions/trillions of files of the same format.
i am getting 50Mbps.. copying NAS to tape
For what its worth..
Network Router: TG789vas v2
NAS: Synology DS1815+
Switch: (for Server, Tape Drive, Tape Library & Their Associated UPS ) Airpho Gigabit AR-GS108
Server: X3650 M3 Running Windows 2012 R2
Tape Library: IBM TS3100 3573 L2U
Tape Drive: IBM LTO6 8Gib Fibre Channel 35P1624 Feature Code 8348
Tape Drive Fibre Channel Card: Avago AFBR-57F5PZ
Server Fibre Card: Emulex LPE12002
Using NO compression
I understand the new IBM LTO 8 Drives can get up around 750 to 800Mbps
1. QUANTUM LTO-7 Tape Drive, Half Height, Tabletop 2. Delock Cable Mini SAS HD SFF-8644 > Mini SAS SFF-8088 1 m 3. LSI LSI00343 SAS 9300-8E Host Bus Adapter (8-Port, PCI-e 3.0 8x, SAS 3.0)
Also, there is a couple of useful tape accessories:
4. Cleaning Cartridge (I use one from Quantum) 5. Cases for storing LTO Ultrium cartridges (I use some from Turtle Case, for 20 cartridges each)
i am getting 50Mbps.. copying NAS to tape
For what its worth..
Network Router: TG789vas v2
NAS: Synology DS1815+
Switch: (for Server, Tape Drive, Tape Library & Their Associated UPS ) Airpho Gigabit AR-GS108
Server: X3650 M3 Running Windows 2012 R2
Tape Library: IBM TS3100 3573 L2U
Tape Drive: IBM LTO6 8Gib Fibre Channel 35P1624 Feature Code 8348
Tape Drive Fibre Channel Card: Avago AFBR-57F5PZ
Server Fibre Card: Emulex LPE12002
Using NO compression
I understand the new IBM LTO 8 Drives can get up around 750 to 800Mbps
e.g. 8" HDDs are also cheaper per byte than 5.25", than 3.5", than SSD's.
I doubt your movie collection is large enough that tape would be cheaper. A single tape has about ~50x the capacity of a Blu-ray Disc, but you need to buy a lot of tapes before the whole setup becomes cheaper than HDD.
> I don’t think I will see any benefits of the compression…
Ignore the compression, it’s garbage.
> …the prices seem comparable to just buying a 8TB HD…
By “comparable”… tape is clearly cheaper per byte when you compare prices, it’s just not so radically cheaper that it changes your life.
I have mentioned in another message that the breaking point is around 75 TB or around 50 TB, depending on how many copies you store, i.e. around 1000 to 1500 Blu-ray movies.
I agree that many people, probably most people, do not need to store so much data to make tape storage economical, but for those who have a large enough data archive, like myself, the tape is really radically cheaper to have changed my life.
Obviously, there is a vicious circle, few people buy tape drives because they are too expensive, so that tape drives are expensive because few of them are sold.
If they would have been mass produced, tape drives should have been 5 to 10 times cheaper, and then tape archives would have made sense even for the smallest movie collections.
I was being conservative and using BD XL.
Seems like you came to the same conclusion about the break-even point—around 150TB before you consider replication.
To recover the drive + SAS HBA card costs, the movie collection must be larger than about 75 TB if you store double copies or larger than about 50 TB if you store triple copies.
If you store a single copy of any digital medium, the chances to not lose anything after many years are negligible.
Cheapest new LTO-7 drive is over 3000 USD though, which means you'd need more than 300TB of data for a new LTO-7 tape solution to be cheaper here.
Looking at Amazon USA (just search LTO-7), I see prices between USD 63 and USD 69, or even just $60 per cartridge if you buy a 10-pack. That is still more expensive than where I buy, but it is nevertheless far closer to 3 times less than HDDs than to 2 times less than HDDs.
Though again, with the cost of the drive you need quite a lot of data for it to make sense.
I wonder if this was a typo. Did they mean that LTO-8 tapes are out of stock? Otherwise, the sentence structure "even if ... are now in stock, you can buy ..." is kind of weird.
> reformat them to M8 and get 9TB of native storage (22.5TB compressed).
What does this mean? Doesn't how much it compresses depend on the data not the storage device?
https://www.google.com/shopping/product/10502190238469223139
Google says
"HP LTO-8 Ultrium, 30 TB, RW Data Cartridge Tape. Exhaustively tested, HPE LTO Ultrium cartridges meet all your demands for maximum reliability when restoring data, offering high storage density, ease of management and scalable storage and backup performance."
TapeandMedia.com says
"1 - HPE LTO Ultrium 8 Tape with a capacity of 12 TB and up to 30 TB compressed capacity."
Here's a 15TB compressed for $63:
https://www.amazon.com/HP-C7977A-Cartridge-Compressed-Capaci...
LTO-8 drives can also use blank LTO-7 media to get density halfway between LTO-7 and LTO-8; this is referred to as LTO-7 Type M, or Type M-8. This applies to the raw storage capacity, not just the compressed capacity (which is conventionally referred to with the assumption of a 2.5x compression ratio, even though not all real-world data is compressible).
I don't understand this point. Why would tape allow compression that other forms of media don't?
But this kind of compression can be better achieved I think with one core of your CPU, plaintext compression of 3x shouldn't need lzma (and if you really need to compress 22TB of plain text with no binary or multimedia files, well maybe you could compress it slightly with lz4 or a simple zlib compression before sending it).
Compression may have been a big deal in the ages of sub-1Ghz single core systems but not anymore. Especially since you ought to be encrypting before writing anyway.
Why does it continue? Probably so they can double the capacity that they put on the tape label, which is always the compressed capacity and not the native or real capacity. Plus backward compatible with such encoded tapes.
The data files that I am writing to the tapes have their metadata written into a database to be able to retrieve them in the future, then I group them in chunks of an approximately fixed size (50 GB in my case), then I compress them, then I encrypt them and then I add some redundancy (with par2) for error recovery. A simple solution for compression with encryption is the lrzip program, but for more flexibility in encryption you could use e.g. the openssl program invoked with the desired parameters. There are many encryption programs and any of them is better than using the encryption option of a tape drive.
So I queue the files to be written on the tape in a directory and when the size of the directory exceeds a threshold (50 GB in my case) a script is invoked that does the processing mentioned above, including the encryption, then it writes the result on the tape. A similar script does the inverse operations when I retrieve a file or group of files from the tape, giving its position as a tape number + a tape file number as obtained from the file database.
https://aws.amazon.com/snowmobile/
...putting stuff on a big truck is a very viable alternative to using a series of tubes.
Backups aren't valid until they're tested.