deep_kkumar (4/12/2013)
so that one instance running on node B and node c never fails over to node A.
Simple don't install the instance to NodeA 😉
If you do install the instance to NodeA, just ensure you remove NodeA as a possible owner on the cluster groups virtual network name resource for the instance in question.
deep_kkumar (4/12/2013)
I also like your idea of masking the disks. Which one you suggest ?
Not sure what you mean here.
deep_kkumar (4/12/2013)
Actually my requirement is to setup 4 node cluster with instance 1 to run on node A and node B. Instance 2 runnig on node B and node C. Instance3 running on node D and node B.
You'll need either a disk resource, if all nodes are on the same site, or a fileshare if they're geographically dispersed.
Hmm, the following solution would also be viable as follows;
Instance 1 on NodeA and NodeD
Instance 2 on NodeB and NodeD
Instance 3 on NodeC and NodeD
Make NodeD a higher spec\capacity box than the other nodes so that it can handle all resources failing over at once if they ever needed to.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉