« Previous Next »

Thread: MSCS / Failover clustering and IIS 7.0

Last post 10-29-2009 4:57 AM by steve schofield. 24 replies.

Average Rating Rate It (5)

RSS

Page 2 of 2 (25 items) < Previous 1 2

Sort Posts:

  • 10-23-2008, 1:10 PM In reply to

    • kruda
    • Not Ranked
    • Joined on 06-13-2008, 11:01 AM
    • Posts 5

    Re: MSCS / Failover clustering and IIS 7.0

    Does NLB get an IIS error i mean does it recognize that IIS Service is down or only that the machine is down ?

     

    Regards

  • 11-24-2008, 3:00 PM In reply to

    Re: MSCS / Failover clustering and IIS 7.0

    Server 2008 NLB doesn't support Stretch Clusters does it?  With MSCS I am able to build a Strech Cluster between my Datacenter and a DR site.

  • 11-24-2008, 4:12 PM In reply to

    • kruda
    • Not Ranked
    • Joined on 06-13-2008, 11:01 AM
    • Posts 5

    Re: MSCS / Failover clustering and IIS 7.0

     Well i am using MSCS with Server 2003 and IIS 6. To get a applicatin cluster aware i am using generic service which works very fine but i am not able to recognize if my application is hanging. with generic service i can only failover if my server is dying.  To recognize that my application is not working anymore i have to make the application itself  cluster aware or using my way, namely a generic script implementing the enty point functions.

     

    I hope this will work in a few days also .

  • 11-24-2008, 4:22 PM In reply to

    Re: MSCS / Failover clustering and IIS 7.0

    I too had it working acceptably with 2003 and IIS6.  But now we are upgrading to 2008 and IIS7 and I need to be able to cluster my Exchange 2007 CAS role accross multiple sites.   I'm working with it in my test environment at the moment, but not with much success. 

  • 04-19-2009, 10:27 PM In reply to

    • Kanien
    • Top 75 Contributor
    • Joined on 01-31-2008, 12:14 AM
    • Posts 104

    Re: MSCS / Failover clustering and IIS 7.0

    if the choices are NLB vs MSCS the reason someone would hypothetically want MSCS is for service checks.  Am I wrong in my assumptions that NLB doesn't do service checks and uses another mechanism for knowing whether a node is available?  For example if one of the web nodes responds to ICMP, but the web service has failed the request would error out right?

    In this same scenario if you had MSCS Active/Active on IIS7 it would know the web server wasn't responding and wouldn't pass the request...ideally..but I'm told that MSCS on 2k8 doesn't work for IIS7.

  • 04-19-2009, 11:08 PM In reply to

    Re: MSCS / Failover clustering and IIS 7.0

    If you are using a hardware load-balancer, you can do basic service level checks and take nodes out of rotation if they are not responding.  NLB doesn't have this, if you wanted to use NLB from MS, then you'd have to monitor each node (each domain on each node) and alert.  If an alert came up, the alert action could disable the site.  That wouldn't be very pretty but it would work. 

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 04-20-2009, 11:43 AM In reply to

    • DClayton
    • Not Ranked
    • Joined on 04-20-2009, 3:16 PM
    • Posts 1

    Re: MSCS / Failover clustering and IIS 7.0

    Hi to all,

    I currently have my web platform running on a 2 node cluster using Server 2003 and IIS6.  I have two cluster groups; one for SQL Server and the other for IIS.  This provides me a robust solution as i can have a SQL running on one server and IIS running on the other.  This allows me to utilize both servers and also the reliability that either server fails, the other will pick up the cluster group and run both simultaniously.

    I am looking to upgrade to Server 2008 and after reading this post, I am wondering if I am setting my website up correctly.  I have two physical machines and a SAN and I want to get the best in terms of reliability and performance.  The main problems with the current setup are as follows:

    a) If IIS crashes or the application pool fails to recycle, the group doesn't failover.
    b) Any application / IIS changes have to be made on both nodes.  IIS allows you to export the metabase and re-import but custom .Net installations do not.  If we upgrade the app, it has to be done on both nodes independantly.

    Some other considerations are:

    a) I have multiple sites running within IIS, each with their own IP currently controlled by MSCS.
    b) I have file shares for the various site setup, again managed by MSCS.
    c) I don't want to loose the ability to have shared resources between two nodes, for example, can NLB allow me to have file shares etc and not require me to set them up independantly on each server. 

    What would people recommend for setting up the two machines, preferably with Server 2008?  My main site comprises of the application (installed to C:\), the IIS structure (installed on I:\), and the SQL data (installed on E:\).  Any suggestions would be very welcome.

  • 07-09-2009, 2:38 PM In reply to

    Re: MSCS / Failover clustering and IIS 7.0

     I just came across as I'm about to try clustering IIS 6.  In my 8 years of being an IIS Admin this will be my first attempt at clustering, so it should be fun. :)

     The reason we are doing this is because we are installing a 3rd party ERP app which requires IIS to be loaded on the app servers, which also run Websphere.  Those servers will be using MSCS to provide redundancy, so that means I need to install IIS to the cluster.  I found that HP article earlier.  Any other advice or resources I should look at?  Thanks guys.

  • 07-09-2009, 4:39 PM In reply to

    Re: MSCS / Failover clustering and IIS 7.0

     Probably better off starting a new thread.

    I would advice on a hardware load balanced frontend and then have a db in a cluster environment.

  • 10-29-2009, 4:57 AM In reply to

    Re: MSCS / Failover clustering and IIS 7.0

Page 2 of 2 (25 items) < Previous 1 2
Microsoft Communities