I
Ian Addis
I have a .NET app and two web servers. One was designated as a
redundant server, to be brought into service (manually) if the primary
server failed. However this seems a bit of a waste when I have
Windows 2003 and hence I have Network Load Balancing at my disposal.
Each server has two gigabit network cards. The cards are teamed for
load balancing and redundancy. If I set up NLB, apparently I need to
reserve 1 card for NLB and one for host-to-host communication. This
means that I lose the load balancing and redundancy features of having
the cards teamed.
For reference, both servers will be connecting to a single MS SQL
Server (log shipped to another server for manual redundancy) running
SQL 2000 and Win 2003.
Should I set up NLB and disable the NIC teaming? Will setting up NLB
as a multicast cluster remove the need for a dedicated host-to-host
NIC?
Answers greatly appreciated!
Regards,
Ian A.
redundant server, to be brought into service (manually) if the primary
server failed. However this seems a bit of a waste when I have
Windows 2003 and hence I have Network Load Balancing at my disposal.
Each server has two gigabit network cards. The cards are teamed for
load balancing and redundancy. If I set up NLB, apparently I need to
reserve 1 card for NLB and one for host-to-host communication. This
means that I lose the load balancing and redundancy features of having
the cards teamed.
For reference, both servers will be connecting to a single MS SQL
Server (log shipped to another server for manual redundancy) running
SQL 2000 and Win 2003.
Should I set up NLB and disable the NIC teaming? Will setting up NLB
as a multicast cluster remove the need for a dedicated host-to-host
NIC?
Answers greatly appreciated!
Regards,
Ian A.