Design Con 2015
Breaking News
Memory Designline Blog

Biting into exabytes

View Comments: Newest First | Oldest First | Threaded View
Paul A. Clayton
User Rank
re: Biting into exabytes
Paul A. Clayton   3/3/2011 6:58:49 PM
To provide something closer to random access, would something analogous to microfiche (relative to microfilm) be practical? For a robotic library, handling a much larger number of fiches than tape cassettes might not be a huge problem. The density might be significantly lower, requiring (thinner) per-sheet protection rather than (thicker) per-spool protection, but the faster access to arbitrary data might be a sufficient advantage. A less related question: Would thermally assisted writing make archival storage more reliable by preventing magnetic fields at room temperature from corrupting the data?

User Rank
re: Biting into exabytes
Sheetal.Pandey   2/9/2011 12:13:53 AM
wow thats great. With the growing needs of family and business responsibilities I guess it wont be a surprise when people satrt demanding that. Of course cost is the most decisive factor. What will be the cost anyway???

User Rank
re: Biting into exabytes
tdenesyk   2/8/2011 2:59:21 PM
I think the title of this article is misleading. I've been unsuccessful finding any mention of exabyte (10exp18 bytes) in the Oracle announcement. Or in the text of this article in relation to this product. 5 TB is a long way from 1 EB. Btw, at 240 MB/Sec it'll take on the order of 10exp 9 seconds - 132 yrs of continuous writing to fill a 1 EB tape.

User Rank
re: Biting into exabytes
DMcCunney   2/7/2011 5:22:08 PM
Game changer? I doubt it. The advantage of tape for backup is cost. Tape is cheap. The disadvantage is time and convenience. It takes a relatively long time to back up to tape, and restoring is a pain because it's a sequential medium and you must start at the beginning and advance to the spot where what you want is stored before you can restore it. And backup systems have catalogs that take space, so you may even be looking at regenerating the catalog first so you can find the file on the tape. I was the backup admin at a former employer, and I was pushing hard for a two stage strategy: back up to disk, then tape. Corporate standards required us to back up every night and send the tapes offsite in the morning. Guaranteed, a user would discover they had trashed a file and needed a restore just *after* the tapes had been sent off... We also had a division that couldn't *do* a *full* nightly backup to tape, because there wasn't enough time in the backup window. They had to hope an incremental would suffice. In my view, backup would go to disk, and from disk to tape. The disk backup would be there for the "Oops! I trashed X! Can you restore it from backup?" instances, and the tape would be long term archival storage. I see the same when you are dealing with potentially exabyte sized backups. They aren't your primary backup - they're a long term archival solution. Oracle's announcement says it will be faster, easier, and cheaper to create such backups, but you still hope you'll never have to restore from one.

More Blogs from Memory Designline Blog
Forget about Startup: Silicon Valley and pitch meetings—let’s show what engineers can really do when put to the test.
Jim Handy talks about the Cypress-Ramtron deal and the future of FRAM.
Learn about testing DDR4 and reasons to migrate to the standard at the October 30-31 event in Santa Clara, California.
With a few hundred dollars and a secondhand camera, engineering student captures images of the Earth’s curvature.
Find out what STEC discovered during virtualization show.
EE Times Senior Technical Editor Martin Rowe will interview EMC engineer Kenneth Wyatt.
Top Comments of the Week
Like Us on Facebook Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed
Flash Poll