Re: Request for information
- From: "Russ Kaufmann" <russ.kaufmann@xxxxxxxxxxxxx>
- Date: Tue, 20 Jan 2009 22:39:53 -0700
"Robert Smit" <Robert.smit-nospam-aca-computers.nl> wrote in message news:exKOImteJHA.5428@xxxxxxxxxxxxxxxxxxxxxxx
The IIS section I would do this in a web farm there are good papers on this. But do this in a team with your web site developers not all sites are best designed for NLB.
Two servers with 2 nic's ( LAN /NLB ) for the IIS , with a DFS for the site so you need only to update the website in one location.
NLB with Unicast no longer requires two NICs. You can get by fine with a single NIC. Also, you don't need DFS to make it work. The key is keeping all NLB'd servers consistent with the same data, etc. You can also use a clustered file server for the data if you really want to go nuts.
Two node Cluster for your mail and SQL. IF this is supported with mailenable.
It is never a good idea to host two heavy workloads on the same cluster as in a failure, you must support both on the same physical node and it can result in extremely poor performance.
I think ISCSI is the most flexible solution, make a storage lan, public and private lan all in different IP subnets !! use separate storage switches and lan switches.
iSCSI and Fiber are your real choices when it comes to enterprise level support. Expect to pay a pretty penny.
Good luck, and have fun.
--
Russ Kaufmann,
MVP, MCSE: Messaging and Security, MCT, MCITP, MCTS and other stuff
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
.
- References:
- Request for information
- From: Roger
- Re: Request for information
- From: Robert Smit
- Request for information
- Prev by Date: Re: Using cluster.exe to create physical disks
- Next by Date: Re: Networking configuration recommendations
- Previous by thread: Re: Request for information
- Next by thread: SAN lifecyle
- Index(es):
Relevant Pages
|
Loading