Graceful failover

Hi George,

 

 

Thanks for the reply. I have more info and would like you to clarify a point if possible?

 

 

You mentioned getting the developers to wait 30 minutes for the failover to happen. Could you confirm how you would do the failover? You see we are doing this by disabling the pool member on the gtm however the number of connections never seem to go down - well only by a small amount. We've even left it on over the weekend and the connections seem to still exist after a long period of time.

 

 

The other part of this project is to do with Internet Explorer. It seems IE has it's own internal dns cache. When we perform a failover (by manually stopping the web service on the web server) our test systems using Firefox and Chrome pretty much continue without any problems - you might have to press F5 once or twice. However with IE the only way we can get our session to continue (i.e. so we can carry on browsing the site) is to close the browser down and start a fresh instance. We don't require any session data to be carried over with the failover, we just need the browser to be able to continue browsing the site thereby not inconveniencing the customer.

 

 

Hopefully that makes sense. All we want these boxes to do is failover without causing any disruption. It seems we're unable to do this. I hope this is due to a lack of understanding on our behalf and not the 'features' of F5 and Microsoft products.

 

 

Thanks,

 

 

Joe