Thanks for the input folks. I’ve solved the issue and here are the details logged here for anyone else that might run into this.
- DPM 2010 - Microsoft Data Protection Manager 2010 (I was wrong in the original post…doh!) on Windows 2008R2, 250 GB C: partition, 250 GB D: partition.
- Server hardware: Intel SR1630GP, 16 GB RAM, 2x500GB WD 7200RPM SATA drives (mirrored), Dual onboard Intel NICS (852574L & 82578DM), Intel Xeon X3450 @ 2.66ghz (quad core w/hyperthreading so 8 processes).
- Drobo Elite with 8 WD 2TB drives, both NIC’s assiged static addresses.
- One server NIC assiged to VLAN for storage, the other on the server VLAN. Both DROBO NICs on the Storage VLAN with static addresses all around.
I followed the instructions found here about setting up the volumes via USB connection and not formatting them. Shutting the DROBO down, bringing it back online and connecting via iSCSI. Once the connection is established via iSCSI it is important to note the connection strings.
For instance I setup 4 4TB volumes. The iSCSI Names showed up as:
Plus one bonus as:
Do NOT try to format the connection to the .management LUN!!! I kept doing it and it will cause things to NOT WORK in a very inconsistent manner. Now, in my defense, I didn’t count the number of connections and it took fresh eyes to see there were 5 instead of the expected 4 (yeah, I’m being hazed about it…rightly so.) and I didn’t expand the name field to see the entire string. Once I did that it was pretty apparent what I had done wrong.
Last tip: format the drives as GPT and make them dynamic in the Disk Manager but don’t put any partitions on them. DPM likes to do its own partitioning thing on the free space of a volume. I found that if I made the disk dynamic in Disk Manager it worked every time (I tried it about 7 or 8 times before I figured that little gem out.).
Oh one more little thing: I took bhiga’s advice about bottlenecks to heart. I found the best performance was to use both DROBO IP’s as targets and enable multipath on all 4 volumes. I plan on putting another dual NIC in and bonding it but wanted to get some good backups going before the weekend and the NIC hasn’t arrived (curse you red baron!) as of last night.
I think that is it. We’ve been online for a week now with no problems. Before I would have some time out issues as bhiga pointed out.
I hope this helps someone, and as usual, your mileage may vary. Please note that this is the final configuration that I came up with as a compromise of simplicity and ease of management and lots of little partitions…
Go Army! Beat Navy!
Derek Kruger, MCSE, MBA - IT Management