>I am looking to setup 2 node cluster, windows server 2003 with one local
> drive on each machine. I will also use shared storage connected via
> iscsi.
Excellent, a good base for a 2-node failover cluster, ensure you are running
Windows 2003 Enterprise on both nodes
> This shared storage will house sql server 2005 and it's db files. In
> addition active server will server IIS application.
Well the shared storage will host db files only, as the SQL binaries are
installed on the individual hosts.
SQL is going to be install in the cluster, so you first cluster and then
install SQL
(various good whitepapers on this topic, search with your favorite search
engine)
>
> What I would like to do is to have single ip address pointing to the
> cluster irregardless of which one is active. What do I need on the
> network
> side to make this happen?
2 Network cards is the minimum, 1 for Client traffic (also called public
network), and 1 for cluster traffic (also called private network).
The private network or heartbeat network is best done with a Cross-over
cable if you only have 2 nodes.
Network Teaming is not supported in Windows 2003 for load-balancing, for
failover only it is (on certain cards, but only supported by your network
card vendor, not by MS)
> I am using dell 1955.
Now the important step: In order to be supported for Windows 2003
clustering, the full cluster solution needs to be on the Microsoft Cluster
HCL.
As you are using Dell servers, I am sure that your Dell account manager can
help you with this.
Note: for Windows 2008 and 2008-R2 you do not have a Cluster HCL anymore,
running and passing the cluster validation is the only thing required for
being supported.
>
> Thanks in advance
Good Luck with your project, please let us know if you have more questions.
HTH,
Edwin.
|