I'm setting up NLB on a windows 2008 standard edition server running IIS7 (among other things of course). I have a cluster already set up in a virtual environment using one nic per server and multicast mode. I'm now ready to move this into production and have a beefy machine that has two NICs in it.
I've read several articles about unicast versus multicast...but nothing really for my exact problem. We have two offices hooked together by a WAN. I'd like to set up a web server at each location using NLB so that if one site's internet connection goes down, the other server will continue to serve up my web page.
At each location, other servers with dual nics are teamed up and plugged into seperate gigabyte switches to ensure connectivity if one switch dies.
I'm now stumped as to if I should configure each server in the NLB cluster to use teaming (and split their connection across switches) and Multicast mode, or use one NIC with Unicast. If I go for the latter, if that connection's switch dies, I have to rely on NLB to relay the new requests to the new server even though this server still has one nic plugged into a good switch.
Can anyone offer any advice?