Ok, here’s my plan. I want to have multiple smart volumes on my DroboPro. These will include a 16TB NTFS partition (Accessed from Vista), another 16TB NTFS(Accessed from Win2008Server, maybe even 2 Windows2008Servers running cluster mode), a 16TB HFS+ partition (Accessed from OSX Server), a 2TB ext3 (Accessed from Linux), and an 8TB ext3 or ext4(Accessed from Linux).
I have read the ESXi Best practices document(which seems to be the only document giving advice on multiple clients), but it leaves me with all kinds of questions, like these:
The Best Practices document describes doing a one-time setup of the DroboPro via USB and then from what I can tell, the DroboPro from that point on is not connected to any dashboard. That means there are no notifications or anything in the case of problems? Is there a way to keep a dashboard on this thing? You can read my other posts on this forum to get an idea of my opinion of the lack of information coming out of the DroboPro.
It is stated that port 3260 is for a single client, but 3261 is for multiple clients. But how does this actually work? If I want multiple clients, do I hook the first one (the one with the dashboard) up to port 3260 and the rest to 3261? Or just put all of them on 3261? Will the dashboard work on port 3261? Can I even use a dashboard when I have multiple clients?
Does the DroboPro Mac iSCSI client have any way to configure it to use port 3261?
I’m going to stumble blindly ahead if I don’t get any help, and I’ll let you know how it goes. But if anyone out there has blazed this trail before me already, I’d be interested in hearing your tips…[hr]
Well, here’s what I have so far:
First, I set up a 16TB NTFS, a 2TB NTFS, and an 8TB NTFS on the DroboPro using dashboard on Vista. Then I went into Disk administrator and disabled the 2TB and 8TB volumes. So Vista now just shows me the 16TB volume.
Then, I went into the iSCSI Control Panel and removed the entry for the DroboPro that was operating on port 3260, and replaced it with one on port 3261. After a reboot, I once again had access to my 16TB volume, and the 2TB and 8TB are still disabled.
Then, I started up my OpenSuSE 11.1 machine, and used YaST to set up an iSCSI client connection to the DroboPro, being careful to specify port 3261. All three volumes became visible. So I did mke2fs -j on the 2TB volume. It is still running, and my network graph shows a pretty constant stream of about 15MB/sec as it creates the ext3 filesystem.
While this filesystem is creating, I have gone back to the Vista machine and created and removed a couple folders on the 16TB NTFS volume, which works fine.
So, I have both Linux and Windows Vista accessing separate volumes on the DroboPro, with no crashing. So far so good. More demanding performance testing will be coming soon.
… oh, and as soon as I switched Vista iSCSI to port 3261, the Drobo Dashboard fails to connect to the DroboPro.