GlobalSan Initiator with Xsan
Posted 19 March 2012 - 02:56 AM
Posted 19 March 2012 - 11:20 AM
We are having difficulty telling if your Drobo S or an FS model. The FS model offers no eSATA but offers a NIC, while the S model offers no NIC but has eSATA.
Assuming your Drobo is connected to your Xsan server via eSATA, you will need an iSCSI target running on our Xsan server so it can accept iSCSI connections. You will also need an iSCSI Initiator on each client you wish to connect via iSCSI.
With globalSAN, we offer both. You can install globalSAN's 'Xtarget' (iSCSI Target) on your Xsan server and globalSAN's iSCSI Initiator on each workstation to provide a complete iSCSI solution for both your servers and your clients.
Edited by SNSbarry, 19 March 2012 - 12:21 PM.
Posted 20 March 2012 - 02:11 AM
Posted 20 March 2012 - 04:00 PM
Posted 22 March 2012 - 06:40 PM
If you're going to use iSCSI with XSAN, you still need to follow the best practices for setting up an XSAN environment, replacing Fibre Channel connected storage with iSCSI connected storage. XSAN requires separate Metadata controllers, a GbE metadata network (separate from the iSCSI network), a dedicated LUN for metadata, and then storage pools available for Media.
Aside from it's lack of network functionality I don't think you're going to pull all of this off with your Drobo.
As Barry mentioned, you can use our Xtarget software to present your Drobo S as iSCSI storage for other users. If you're to use this storage as such with an XSAN environment, then the system running Xtarget would need be dedicated to only bridging storage to iSCSI, not also acting as an XSAN client or MDC.
You can also use Xtarget with our iSANmp software, which offers a simple alternative workflow to an XSAN network, and does not require metadata networks, metadata controllers, or metadata LUNs, and it can run on the same system as the Xtarget software as well.