I’ve got my DroboPro with 4 2TB drives setup and a single 16TB volume presented to a Windows 2003 server running on an HP DC7900 ESXi 4 host. I use the Windows 2003 server for file sharing and domain services (DNS etc.). I should add this is just for home use.
I also have a Windows 7 VM on the same ESX host, which I use for downloading torrents - some are HD/1080 torrents, so pretty big.
I have an issue whereby the torrent client reports my drive as not being available. The drive is the shared volume from the Windows 2003 server. The drive is essentially momentarily dropping off the network whenever I try and add a new torrent which is 1080 - i.e. when the torrent client tries to write the 10,20+GB files for the torrent to the drive (the Drobo), the drive drops off and all the torrents stop and fail, due to the drive not being there. The drive IS there, it’s just dropping out while the large files are written.
I have 4 drives, 4 spindles, GB network, 2GB and 2 vCPU’s for each of the 2 VM’s - I shouldn’t have any issues. All of the ESX monitoring shows the resources are very under utilised - including CPU, network, I/O. My VM’s showing no issues with paging, memory or network etc.
I’ve been through the Microsoft Windows 2003 performance tuning for a file server (I’m a virtualisation architect so I know what I’m talking about) and checked everything - i can’t find any reason for this issue.
Importantly, if I point my torrent client at my DLINK DNS-323 which has 2 2TB (same model as the Drobo drives) mirrored in it - no issues. That too is on the same GB network - connected to the same switch etc.
There is VERY little information available from the Drobo software about what’s going on under the hood - it’s a big-miss as far as marketing the device as a SMB storage SAN, when you can’t tell what’s going on.
Anyone else got any thoughts?