Drobo: all 25 reasons (so far) not to put one into production

Yesterday I posted “Reason 25 not to use a Drobo” and refereed to an earlier post listing another reason. Some folks have asked what the other 23 are. My running list so far, in no particular order: (note this is specific to the DroboElite, I haven’t had the misfortune of playing with the rest of their business line yet)

no redundant power supply
no redundant controller
no redundant NIC (two build-in NICs share a controller)
updating firmware requires loss of access
no one point of contact for support (drive manufacturer/Drobo)
no snapshots
no replication
no resizing volumes
no restricting access by IP address/range
no restricting access by iqn
no VLAN
no LAG/LACP/trunking
only one local user
no performance statistics
no troubleshooting capabilities
no user-readable log files
no OOB management (you configure with the USB then it never works again?)
very long rebuild times
very limited management
changing formats on a volume toasts the unit
no SNMP
no phone home
one email alert (can’t send “all” to one user and “important” to another)
expensive for what you get
And Reason 25:the accepted way to change formats is to copy all the data off

This entry was posted in Computing, Storage, Vendor rant and tagged , , . Bookmark the permalink.

2 Responses to Drobo: all 25 reasons (so far) not to put one into production

  1. Tim Clevenger says:

    Reason number 26: Despite the ads that told you that you could throw any old drive into the unit, it in fact has the same problem as other RAID units: consumer (non-TLER) drives can get thrown out of the array. This fact is discussed in the Drobo forums nowadays, but when I bought my DroboFS years ago, the major selling point in every ad was that you could collect up all of the old drives you have laying around and “give them new life” by building a Drobo RAID with them. After losing my array several times to multiple drive failures using brand new consumer-grade drives (that later tested just fine), I swapped in WD Reds and haven’t had a problem since.

    Due to many of the reasons you posted above, this unit now has been relegated to storing ephemeral data that we don’t mind losing.

  2. not sure says:

    Reason 27: No Domain support
    Reason 28: No ability to create Groups

Leave a Reply