Some of the most important technology programs that keep Washington accountable are in danger of being eliminated. Data.gov, USASpending.gov, the IT Dashboard and other federal data transparency and government accountability programs are facing a massive budget cut, despite only being a tiny fraction of the national budget.
Help save the data and make sure that Congress doesn’t leave the American people in the dark.
What’s the motivation behind this post? It’s simple. For Ligia’s Kitchen, it costs me about 10.5 GB for 5 minutes of final, edited footage of show, with a one-camera setup. What goes into the 10.5GB? There’s the raw footage (and sound files, if I use a standalone mic), the edits, and the final, published footage. When I use two cameras, the space needed can easily go up by 1.5-2.5x, depending on the shots I need to get. I shoot and edit in 1080p, and output to 720p.
My storage needs are okay for now. I’ve got plenty of space, and if I keep going at this rate, I should be fine. But… and there’s always a but, isn’t there… I have more show ideas in mind. And there’s the hypothetical possibility of shooting with a RED camera at some point in the future, if certain factors come together to allow it. So I’m thinking ahead.
Current hard drive technology (bits of data on disks) has certainly come a long way. Those of us who’ve been in the business long enough know what prices used to be like for capacities that are laughable by today’s standards. Back in 1999, I paid $275 for a 27GB hard drive. My laptop’s drive in college could store a grand total of 120MB. And when I began to learn programming, I’d load the code into memory from tape…
I remember being really excited about Hitachi’s new Perpendicular Magnetic Recording Technology, which came out in early 2006. They even had an animation on their website, which they’ve taken down since. That technology is behind all of the new hard drives that are on the market today, by the way. Hitachi came up with a way to get the bits of data to stand up (hence the term perpendicular) instead of lying down on hard drive platters, thus doubling the amount of data that could be stored onto them.
There are two roads ahead when it comes to data storage, of which one is more likely to succeed:
Optical storage (this is probably the future of storage)
Biological storage
Let’s first look at biological storage. One particular article made the rounds lately: researchers at the Chinese University in Hong Kong have managed to store 90GB of data in 1g of bacteria. While it sounds exciting, the idea of storing my data in petri dishes on my desk doesn’t readily appeal to me, and certain complications come up:
1g of bacteria is about 10 million cells (that’s a LOT); one must start thinking about the potential for bio hazards when you work with bacteria.
The data is stored in a bacteria’s DNA, which means it’s encrypted (a good thing), but it’s also subject to significant mutation (a bad thing) and it takes a long time to retrieve it because you need a gene sequencer, which is tedious and expensive (a bad thing).
I’m not against this. Hey, if they can make it safe and fast, okay. But I believe this is going to be relegated to special applications. The article suggests the technique is currently used to store copyright information for newly created organisms (I wonder how many new bacteria researchers as a whole have created, and is it any wonder antibiotics have such a hard time working against them when we keep playing God). I also see this sort of data storage as a way for spies to operate, or for governments to keep certain secrets.
Okay, onto more cheery stuff, like optical storage. I’ve always thought there was massive potential here, and am glad to see significant work has already been done to make this a reality. There are two technologies which are feasible, according to research that’s already been done:
HDSS (Holographic Data Storage Systems), which so far can store up to 1TB of data in a crystal the size of a sugar cube, but doesn’t yet allow rewrites
3D optical data storage, which so far can store up to 1TB of data onto a 1.2mm thick optical disc
These developments are very encouraging. Optical storage is safe, and its potential capacities are huge, possibly endless. And when you think about computer hardware, and how manufacturers are looking at using optical technology in the bridges and buses and wires inside the hardware, because it’s incredibly fast, you start to see how optical makes sense. Let’s also not forget fiber optic cabling, and its incredible capacity to carry data. It certainly looks like optical is the future!
So what’s going to happen to the standard 3.5″ form factor of today’s hard drives? Well, it’s likely that it will stay the same, even though it the storage technology inside it might change. We’ll have crystals and lasers instead of platters and heads, but they’ll likely be able to fit them in there somehow. I don’t think we’ll need to start keeping crystal libraries on our desks, like in Superman’s Crystal Cave, and sticking various-sized crystals into our computers any time soon, although it did look pretty cool when Christopher Reeve did it in the movie.
It really all depends on how soon this new technology will come to market. Right now, there’s clearly enough vested interest in the 3.5″ and 2.5″ form factors to motivate drive manufacturers to shoehorn the new technologies into those shapes, but if optical hard drives won’t be here for the next 5-10 years, then it’s possible that the form factor will change as well. We are after all moving to smaller, sleeker shapes for most computers, notebooks and desktops alike.
Updated 11/01/16: I’ve revised my opinion of CrashPlan. See here for the details.
Last week, I wrote an article called “What’s On Your Drobo“, and in it, I mentioned that I was going to try to use an app called CrashPlan to do backups from my photo library in Romania to my backup location in the US. I’m happy to say that it works as expected, and no, this isn’t an April Fool’s joke. Here’s a screenshot of an active backup. At the time, I was getting 2.7 Mbps throughput.
There is a bandwidth bottleneck somewhere, though I’m not sure where it is. My broadband connection in Romania sits at 30 Mbps up and down, as I mentioned here, and my parents’ broadband connection clocks in around 16 Mbps down and 4 Mbps up. Theoretically, since I’m uploading and they’re downloading, I should be getting at least 15 Mbps, but I’m not. So it looks like there’s either a bottleneck as my data exits Romania, or as it goes through the transatlantic fiber optic cables. If someone can chime in on this, I’d love to find out more. I do know that I hit that same 2.5 Mbps ceiling as I upload to SmugMug, YouTube and blip.tv.
Bottlenecks aside, I’m just happy I can do off-site backups, and at least given my current setup, it’s free! CrashPlan works as advertised! I have to admit I was a skeptic when I downloaded it and installed it. I figured it would work on the local network, which is where I did the initial backups, but it would surely run into some firewall issues when I tried it from another location. Nightmares of re-configuring my parents’ firewall remotely flashed before my eyes… Amazingly enough, I didn’t have to do any of that! It just works!
So, if you’re interested in doing this sort of thing, download CrashPlan (it’s multi-platform), install it on both computers where you want to use it, configure it (use the help section), test it, then let it do its thing!
One thing I need to mention is that if one of the computers falls asleep, the backup will be paused until it wakes up. Even though I set my parents’ iMac to wake up for network traffic, CrashPlan doesn’t seem to be able to wake it up when I try to start the backup from my end. Keep that in mind and plan your backups accordingly.
The folks at Data Robotics put together a short video that showcases Drobo owners talking about what they store on their Drobos, and asked their Twitter followers what’s on their units.
That got me thinking about what I store on my Drobos. I have four Drobos in total: three 1st Gen Drobo units (USB 2.0 only) and one 2nd Gen Drobo (Firewire 800 + USB 2.0). Perhaps that makes me a bit unusual. Most people have one or two units, not four. But there’s reason to the seeming excess.
For one thing, I have a huge photo library. (You can find the photos I edited and published here.) For another, my wife and I have a huge video library. These are movies and cartoons we had on VHS tapes, which we digitized, or on DVDs, which we archived for easy viewing, or TV shows and movies that we recorded from TV. We’re big fans of classic movies and cartoons from the 1920s, 30s and 40s, and we collect all the ones we like. We also digitized most of our old paperwork. My medical records are all digital. So are my dental records. So are a bunch of our other documents. I scanned all the stuff I could scan, and now when I need to look something up, it’s right there at my fingertips. I’ve also started shooting video more intensively this past year, in SD and HD. (You can find my published videos here or here.) All that stuff takes a fair amount of space — terabytes to be more precise. And to top off this whole list, we live our life on two continents (North America and Europe).
Here’s what I do to make sure I don’t lose my data:
I keep a Drobo with my parents, at their place. On it, I store a backup of my photo library and our video library, along with their files. I back up my live photo library to it using CrashPlan, a piece of software that will let you back up your data to a friend’s machine. I’ve actually just started using it, and while I’ve been able to back up just fine with both machines on the same network, being able to do it from thousands of miles away will be a litmus test of the software’s capabilities. I’ll be sure to write about it if it proves workable. The video library gets backed up every once in a while in a pretty simple manner: I carry movies and videos to them on a hard drive and copy them onto the Drobo. Updated 4/21/10: CrashPlan does indeed work as advertised!
I keep two Drobo units at our home. On one of them, I keep our video library, and an extensive, historical file archive. On another, I keep a mirror copy of my live photo library, which is currently stored on a WD Studio drive, because it’s smaller and easier to transport than a Drobo, and I do a fair bit of traveling. I mirror my photo library with an app called Synkron, which works great. I switched to the WD Studio when I started traveling extensively and realized the Drobo couldn’t always fit safely into my luggage. (Where oh where is that Drobo carrying case I wrote about last year?)
I gave the fourth Drobo to my brother, who needed a solid data storage device to begin to archive his ever-growing library of ethnological videos. He’s a documentary filmmaker who travels around Romania studying and recording religious and secular customs, which are being forgotten and buried along with the old folks. He wants to preserve these things for posterity. You can learn more about what he does at his website, called ORMA.
So that’s how I use my Drobos. However, I’ll have another logistical issue to deal with in the near future. I’m running out of space on the WD Studio drive, which has 2 x 1 TB drives in it. I run it in RAID 1, and in another month or two, it’ll be completely full. I’ll need to start using one of my Drobo units as my primary photo editing/storage device again. This means I’ll shuffle all my data around once more. A possible new arrangement will see me using the 2nd Gen Drobo for the storage and editing of my photos and videos, and the other for the storage and retrieval of our video library and historical file archive, while the WD Studio drive will see some backup duty or be relegated for travel-only purposes.
The current drive distribution among the three Drobos I use actively is as follows:
2 x 2 TB drives + 2 x 1 TB drives in the Drobo that stays with my parents
4 x 1 TB drives and 4 x 500 GB drives, respectively, in the two Drobos that are with us
I can’t speak for my brother, but I believe he’s using 4 x 1 TB drives in his Drobo
I’d love to hear how you are using your Drobo. Perhaps you have some ideas for me?
Image and video used courtesy of Data Robotics. The 2nd Gen Drobo is available for purchase from Amazon or B&H Photo. The 1st Gen Drobo has been discontinued as of 2009. Be sure to also check out my reviews of the Drobo S, DroboPro and DroboElite.
The folks from ioSafe gave me a 500 GB ioSafe Solo drive and asked if I could write about it. The short summary is this: it’s quite different from a regular external drive, and yes, it does exactly what it says it’s supposed to do — it is fireproof and waterproof.
How is it different? For one thing, it’s big — much bigger than a regular external drive, much bigger than even a Drobo. Keep in mind this is a single-drive enclosure, while the Drobo is a four-drive enclosure. It’s also much heavier than a regular external hard drive. The discrepancy is explained solely by its unique purpose, which is to withstand fires and floods. I’ll explain below.
The ioSafe drive is made with technologies like the FloSafe air cooled vent, HydroSafe water barrier and DataCast fire safe — patented technologies which the folks at ioSafe invented.
One of my concerns with the drive, given its watertight and fireproof seals, was how it cools itself. Could it withstand regular use? Wouldn’t the drive overheat during extended use? The answer is no, thanks to the FloSafe vents, which stay open and allow air to circulate through the enclosure as long as the room temperature stays under 200° F. Once the ambient heat passes over that threshold, the vents close and seal automatically, protecting the drive inside. The closing mechanism doesn’t rely on electricity — it’s mechanically triggered, which means it’ll work whether or not the drive is plugged in.
The drive and circuits are packed inside a foam enclosure called the DataCast fire insulation. The DataCast formulation forms a chemical bond with water molecules that, at temperatures above 160° F, releases water vapor to limit the internal temperature of the hard drive. This enables the ioSafe data storage product to protect your data from heat damage while the unit is engulfed in fire. Typical fires last about 30 minutes and have temperatures of approximately 800° F to 1000° F. The ioSafe fire resistant data storage product has been tested up to UL 72 one-hour standards at 1700° F and the ASTM E119 fire curve standard. While the strength and duration of a fire cannot be predicted, the ioSafe drive has been over-engineered to withstand even the toughest fires, and that’s good news for your data.
When it comes to flood protection, the HydroSafe barrier blocks fresh or saltwater damage, including full immersion, while still allowing for the heat dissipation necessary for normal functioning. All ioSafe products are inherently flood resistant, whether or not the vents are open or closed, which is as it should be, since a flood isn’t normally associated with a temperature rise above 200° F.
The official specs of the ioSafe Solo drive which I reviewed say that it’s fireproof to 1550° F up to ½ hour and waterproof to 10 feet of fresh or saltwater up to 3 full days. They also say the drive comes with a 3-year warranty and a $1,000 Data Recovery Service, which works as follows (quoting from ioSafe website):
The Company or its contracted partner will provide phone or email based support to assist in recovering the data, or
The Company will pay for the disaster exposed product to be shipped back to the Company’s headquarters for data recovery. If data recovery is successful, a replacement product will be loaded with the original data and shipped back to the original user, or
At the discretion of the Company, if the data recovery by the Company is not successful, the Company will pay up to the amount shown in the table below for the specific product to a third-party disk recovery service of the Company’s choice to extract the data. Any data extracted will be loaded on a replacement product and shipped back to the original user. The Company has the right to use a factory refurbished product as the replacement product.
Product Line
U.S. Dollars per Disk
S2, R4
$5,000
3.5 Pilot, 3.5 Squadron
$2,500
Solo External HDD
$1,000
I know of no other company that offers a free data recovery service, particularly after a damaging incident such as a fire or a flood. ioSafe does it, proving their commitment to the safety of your data.
Now let’s talk about the other aspects of the drive, such as its looks, performance and noise levels.
The enclosure of the ioSafe Solo is made of solid sheet metal, particularly the front, top and bottom, which is made of a single piece of 1 mm thick steel. It’s built like a tank — as hard drives go, anyway — and is made to withstand hits and dents. The simplicity of the design — two leaves of sheet metal bent into simple curves that fit together like a dovetail joint — makes it appealing to someone who likes good, solid design.
Other than its size, the enclosure’s exterior isn’t fancy or flashy. The real beauty lies inside, in the fireproof and waterproof padding and seals. Other than a bit of branding and the blue LEDs on the front, the sides, top and bottom feature no adornments at all.
The back side features a lip with a punch hole that can be used to secure the drive physically to a flat surface, or with a security cable. The back of the drive has a power switch, the USB connector, the air grille through which the drive cools itself, the DC power port, and a metal plate with the drive’s serial number etched onto it.
Hardware noise is something I’m always concerned with. I prefer my hardware to be as quiet as possible. I compared the ioSafe drive with other external devices that I own, like the 1st generation Drobo, the 2nd generation Drobo, the WD My Book Studio Edition II, and the LaCie Mini. On an approximate loudness scale, it ranks below a 1st gen Drobo but above all the other devices, like the 2nd gen Drobo, the My Book Studio and the LaCie Mini. It’s the fan that’s the cause of the noise, not the hard drive itself. Given how much padding and sealing there is inside the enclosure, the fan has to work extra in order to cool it, so you’ll always hear its hum. The good thing is that it’s constant, so you tend to get used to it after a while.
The drive has a USB 2.0 interface, so you can expect typical USB 2.0 transfer speeds from it (it tops out at 480 Mbps). For example, I was able to copy 122.25 GB to the ioSafe Solo in 1 hour and 50 minutes, which is par, or perhaps even a little faster, than my prior experiences with USB 2.0 transfers.
Beside the size of the drive, which is considerable but appropriate given its specifications and purpose (5.0″W x 7.1″H x 11.0″L), there’s also its weight to consider (15 lbs). This is a heavy drive. It’s not something you can lug around in a backpack. It’s something that’s meant to be stationary and to withstand fires and floods. It is serious business. I wouldn’t even call the ioSafe Solo a drive you can keep on your desktop. Yes, you can do that, but it’s probably better to keep it bolted to the floor or to your wall, or even better, plug it into a USB to Ethernet device and keep it away from your desk, somewhere in the basement, in the attic, or in a closet. Turn it on every once in a while, copy your vital data to it, then turn it off and forget about it, until you have a disaster. Then dig it out, retrieve your data, and pat yourself on the back for having bought it.
The ioSafe Solo isn’t the only device made by ioSafe. They have a whole range of drives that cater to consumers and businesses alike. They have internal drives, made to fit inside existing computers, that use the same fire and water-resistant technology. They’re 2.5″ drives fitted inside custom 3.5″ enclosures with SATA interfaces. They also have rack-mountable RAID systems configured as RAID 1 (mirrors) and NAS devices that can be configured as RAID 0/1/5.
I initially planned to put the review unit through fire and water in order to test it, but I honestly don’t know what new things I could add to what people have already done to it in order to prove its capabilities. Take this video from the Wall Street Journal for example, where ioSafe’s CEO dunked the drive in a pool, then baked it in an oven to show the data stays safe.
Another reviewer barbecued the ioSafe Solo, only to find out the data stayed safe, as expected. On a local TV station in California, where ioSafe is headquartered, Robb Moore, ioSafe’s CEO, went on camera to torch yet another product — their 3.5″ internal drive that uses the same technology. The result, once more, was the expected one. The data stayed safe even though the drive was put through 30 minutes of 1200° F fire.
Finally, Gear Diary ran the ultimate fire test on the ioSafe Solo. They put it inside a burning car, left it in there for 10-15 minutes, hosed it down with professional fire equipment, then disassembled it to see if the data stayed safe. It did.
Like I said, I don’t know what I could add by torching and dunking my review unit, when it’s already been done much better by others. Gear Diary’s test in a burning car was the ultimate proof for me. That was a real test under real life conditions, and the drive proved that it could withstand it.
If you’d like to buy the Solo, you can do so directly from ioSafe or from Amazon.
If you’d like to win your very own ioSafe Solo drive, then join ioSafe’s Facebook page. As soon as they have 5,000 fans, they’ll hold a drawing and award one of them the drive.