To rule out an issue with the Drobo, we briefly tested the performance from various systems. What took between 7-9 minutes on most clients, was estimated with 30 hours on Tiger. When we setup the Drobo we tried to copy 2 GB from various clients to it. I would select a filesystem which still allows you to hook up the Drobo to any of your clients in order to be able to easily recover the volumes in case they decide to stop working.
#DROBO DASHBOARD LINUX MAC#
If you are not using a Mac and keep in a Windows-only environment, it makes more sense to select NTFS, in a Linux-only environment you are save with ext3. If all fails, you can hook it up to the Mac and use DiskWarrior to recover the volume.It would be nice if they provided more details why a Drobo unit would end up in unlabeled state. I googled this and to my surprise there are no information available - Data Robotics keeps it all pretty well hidden behind case numbers on their ticketing system. My friends are using Windows and MacOSX to connect so after some intial problems where they were running FAT32 and the Drobo decided to go unlabeled, we decided to format the unit and use HFS+ instead. The DroboShare costs $200 (USD) and is a glorified Linux server which exports your Drobo using Samba to all clients on the network. Some friends of mine recently bought one of the new Drobo units with a DroboShare.
My files are backed up on a RAID system, I still got plenty of space to waste. I bought a Drobo for myself about seven months ago and I couldn't be any happier.
0 kommentar(er)
