- This topic has 1 reply, 1 voice, and was last updated 9 years, 3 months ago by
.
-
Posts
-
-
We have 2 2006 r2 servers grouped and some of our applications use WCF and IIS to call web services. We had a scenario where we took a server out of load balance, waited for 404’s in IIS and then stopped host instances, shutdown 1 of our servers and it wasnt graceful at all. Messages were lost because they were isolated hosts in IIS on the server being shutdown. How can we add some redundancy to this? I thought the messagebox would pickup the failure and reroute messages to the available one.
I wondered if we could cluster the BizTalk servers therefore clustering IIS providing failover. But does the messagebox really know how to handle that? I’m not sure here…
-
There is no need to cluster IIS. Using load balancing should provide what you need. Load Balancing provides a single IP address for both servers. If one server goes down then the other server will take over all processing. This is done by the load balancing device or NLB way before you get to Biztalk. By removing one server from the load balancing you should not get 404 errors as all traffic should be redirected to the operating server.
The isolated host instances will publish messages to the MessageBoxDb. Any In-Process host instance on any server can process that message.
By removing Server1 from the load balancing should redirect all traffic to Server2, but the in-process host instances on Server1 will continue to process messages. By stopping the host instances on Server1 will mean only the in-process host instances on Server2 will be processing messages.
What type of load balancing are you using? NLB or hardware device?
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.