Optimal Config for a Lab with Limited Hardware
Posted: Wed Jul 15, 2015 10:47 pm
I've been able to obtain two decent servers on which to trial a new SQL2K14 cluster, running on W2K12R2. Each box would be a cluster member.
I also have a PC on which W2K12R2 might run, for example, as the domain controller which might anchor my environment, as well as StarWind.
The question is: if I run Star Wind on one of my two good nodes and tell it to use its spare, non-system drive as an iSCSI drive, can I get away with not using the PC as the iSCSI server? Is there a way to configure the software so that instead of having one IP on the iSCSI lan for cluster node 1, another for cluster node 2, and a third for the target, can I configure one of the cluster nodes so that it offers iSCSI both to itself and the other node?
Basically, I guess, the question is: can I point the iSCSI initiator of the computer running StarWinds at 127.0.0.1?
I also have a PC on which W2K12R2 might run, for example, as the domain controller which might anchor my environment, as well as StarWind.
The question is: if I run Star Wind on one of my two good nodes and tell it to use its spare, non-system drive as an iSCSI drive, can I get away with not using the PC as the iSCSI server? Is there a way to configure the software so that instead of having one IP on the iSCSI lan for cluster node 1, another for cluster node 2, and a third for the target, can I configure one of the cluster nodes so that it offers iSCSI both to itself and the other node?
Basically, I guess, the question is: can I point the iSCSI initiator of the computer running StarWinds at 127.0.0.1?