http://www.drobo.com/
Believe it or not, this is actually going to be a POSITIVE post about Drobo. Bear with me. After my last Drobo post, if you read to the end, you will know that I think this technology is incredible, and I am really mainly disappointed in their lack of attention to customer details. I hold that same opinion, for the most part. However, I think the Drobo product is outstanding.
I have three complaints:
1) See this post regarding formatting Drobo on older Macs. Sadly, as of this date, this has not been fixed. I realize that Drobo can't go back and support every Mac -- but the 32/64 bit issue is one that should be addressed.
2) Drobo's warranty and return policy is lacking. I had a client's Drobo Pro die from a power supply failure at roughly 5 months of age. Because we had not purchased Drobo Care, our only return option was to ship the drive back, then wait for the return. The basic 1-year warranty only covers the hardware, and not shipping, etc. You get 90 days of shipping returns and premium support, but not for the remaining 9 months of warranty.
It's not that you need to buy Drobo Care to extend your warranty after the first year. I would be fine if that were the case. It is that you have to buy Drobo Care to get the SAME service during the first full year — this I object to. It changes after 90 days. Come on — give us the first year. Or, make the warranty only 90 days — I would find that more acceptable than having my warranty tarnish after 90 days.
3) Hard drives in the drive bays of a Drobo unseat too easily. I have a few clients who use pairs of Drobos as network backup. One is kept off-site, while the other is in use, and they are swapped weekly. When you pick up and move a Drobo, the drives can unseat quite easily — while seemingly still in place (ie: they all appear to be seated correctly on close inspection). This can happen even when the drive is handled with kid-glove care. I think the weight of the drives is too much for the design of the latches that hold them in place.
If this happens, when you next plug-in the Drobo, it will report one or more of the drives as missing. Firmly pushing the drive(s) back in corrects the problem — but the Drobo then needs to rebuild for many hours (as many as 40+). This is a vexing problem for one of my clients. So much so that now part of their routine is to re-seat each drive every time they have to change them out.
Now, on balance, I still love the Drobo product. There is room for improvement, but the technology is impressive. For example, despite having drives unseat, my clients have never lost data, nor had to erase and start over with a Drobo.
Now, on to my positive testimonial. For you tech people, this will be a little scary.
One of the cool things about the Drobo is that you can pop-out any drive at any time (assuming the system is working correctly, meaning that your drive status lights are all green). The Drobo will quietly go about rebuilding your data protection and you can go on using it as if nothing happened. I related this fact to client when making the recommendation to him for his backup.
My client purchased a Drobo S and five 2Tb hard drives. The Drobo and three drives arrived almost right away, while two of the drives were delayed a week. We decided to go ahead and deploy, because we had over-speced the storage needs by more than triple in order to provide room to grow. A week later, when the drives arrived, I advised my client that he could simply pop-in the new drives in the empty bays. As it turned out, the top bay of the Drobo wasn't working. Without going into detail, we carefully swaped the two new drives around to demonstrate that it was the Drobo bay, and not the drives, that was the problem. Data Robotics agreed to send out a new Drobo. It got interesting when the new Drobo arrive.
My client, taking me at my word (that you can pop-out any drive at any time), took it upon himself to pull out all four working drives from the old Drobo — without first shutting it down. HE then disconnect the old Drobo, connected the new one, put in the four drives and powered it up. It started blinking Red after it came online, but it came online and all of the data was intact. The red lights worried him, so he called me. I almost had a heart-attack when he told me what he had done. But before I completely panicked, he told me that it mounted and came up just fine. I advised him to wait a few hours to see if it would rebuild and the lights turn green. They did, so he inserted the last drive, it rebuilt itself again, and now his Drobo is fully populated and running like a well-oiled clock.
So, there you have it. This one Drobo recovered from a seemingly impossible event — losing EVERY drive. Granted, there was no data being moved to/from the drive at the time this was happening; plus, I seriously doubt that repeating this "experiment" would result in success; but, my confidence in their technology is high. Any other RAID system I know of, upon losing more than the requisite "safe" number of drives would be a total loss — or, at best, a nightmare to recover.
Hi Bill,
ReplyDeleteI'm a Mac consultant to various businesses, and not an employee of Data Robotics.
While it's definitely a bad idea to eject drives from a Drobo while it is running, I don't think ejecting four drives from a Drobo is the same as four drives failing simultaneously.
As long as the same drive pack is put back into the Drobo, I would expect it to rebuild most of the time, just as your client's did.
The big problem I have with the Drobo products is the drive latch. We have had numerous incidents (four in a row, in fact) where a smaller drive was ejected and a new drive inserted, only to have the Drobo do crazy things: report OTHER drives as failed, or go into a reboot loop, or fail to recognize a drive that had been in the unit only thirty seconds prior, with no additional drives added.
In short, it appears that the drive latch can cause the drive to become unseated during operation, and it appears to us that this happens most frequently during drive replacement. We can't even nail it down to adjacent drives; sometimes replacing a drive in bay 2 will cause bay 4, or bay 5, to fail.
Our largest concern with the Drobo is the seemingly random errors we get. For example, upon replacing a smaller drive with a larger one, the Drobo immediately reported too many drives removed, but even when we reseated each of the drives, the Drobo would randomly report different drives as failed or missing. This has happened with different Drobos, and different drives.
If the Drobo had a locking latch mechanism, like so many other RAID products do, we think this problem could be avoided. For now, we aren't recommending our clients use Drobos because they are just too unreliable.