I have 2 boxes set up with Longhorn Beta 3 running IIS7.
I'd like to know how to configure both machines for failover/clustering
I will eventually be using hardware load balancers in front of them. I understand how to export the configuration from one box to another, but it there a way for both to auto update a shared config file?
Both machines would point to a single shared configuration file. As far as updates, these should be able to update depending on the credentials you supply. What errors are you getting?
I have a shared configuration now. If one of the 2 boxes go down, the pages should still be available? And when the other box comes back up it should auto retrieve the updated files?
Assuming you have 2 x IIS that connect to a Netapp Filer or Fileshare server with either shared config file and/or the web content files... then you have NLB inplace - either Windows NLB or 3rd party hardware. if 1 node is down (entire box - not just IIS
- as NLB is network layer not app layer), then that box is not part of the NLB cluster - all traffice will go to the alive node, when bad node recovered - it will read latest shared config file, etc and business will be usual.
For web - it is recommended to deploy with NLB (active/active) rather than MSCS cluster with active/passive setup.
Sean Connery
2 Posts
Failover/Clustering
May 10, 2007 01:57 PM|LINK
I have 2 boxes set up with Longhorn Beta 3 running IIS7.
I'd like to know how to configure both machines for failover/clustering
I will eventually be using hardware load balancers in front of them. I understand how to export the configuration from one box to another, but it there a way for both to auto update a shared config file?
Thanks.
steve schofi...
5681 Posts
MVP
Moderator
Re: Failover/Clustering
May 11, 2007 12:46 AM|LINK
Steve Schofield
Windows Server MVP - IIS
http://iislogs.com/steveschofield
http://www.IISLogs.com
Log archival solution
Install, Configure, Forget
bills
433 Posts
Microsoft
Re: Failover/Clustering
May 11, 2007 05:19 AM|LINK
Sorry, I don't have good info on how to setup load balancing / fail-over, and it is somewhat dependent on the software/hardware you are using.
But here is the way to set up shared config: http://www.iis.net/articles/view.aspx/Use-IIS7-Administration-Tools/Using-XML-Configuration/Centralized-Configuration?tabid=1
Bill Staples
Product Unit Manager, IIS
blog: http://blogs.iis.net/bills
Sean Connery
2 Posts
Re: Failover/Clustering
May 11, 2007 01:30 PM|LINK
Thanks, that walkthrough helped.
I have a shared configuration now. If one of the 2 boxes go down, the pages should still be available? And when the other box comes back up it should auto retrieve the updated files?
qbernard
5011 Posts
MVP
Moderator
Re: Failover/Clustering
May 18, 2007 07:52 AM|LINK
Assuming you have 2 x IIS that connect to a Netapp Filer or Fileshare server with either shared config file and/or the web content files... then you have NLB inplace - either Windows NLB or 3rd party hardware. if 1 node is down (entire box - not just IIS - as NLB is network layer not app layer), then that box is not part of the NLB cluster - all traffice will go to the alive node, when bad node recovered - it will read latest shared config file, etc and business will be usual.
For web - it is recommended to deploy with NLB (active/active) rather than MSCS cluster with active/passive setup.
Bernard Cheah