Re: Is there a best practise to implement a warm standby-solution

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Chuck. Thanks, but I realize there will be a disruption to the clients
during failover.

All I want to do is reduce the failover time. I can achieve this with a
second instance of the application running in a warm state. The application
is complex with multiple services. If a service fails in the active instance,
I want to know I am failing to an instance of the application that is in good
health (having a better service level than the failed from side). Failing to
the warm instance would only involve a failover of an I P address.

Thanks again for your response.

Hi Chuck. Thanks, but I realize there will be a disruption to the clients
during failover.

"Chuck [MSFT]" wrote:

Microsoft Clustering services cannot provide what you need. We provide
'high' availability, not '100%' availability. Failing over application
'state' is not possible. We disconnect clients during a failover and the
clients must be able to reconnect. If your applications use Distributed
Transactions, then the ACID process should help deal with that.

--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.

"RonC" <RonC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7922DEA4-AE78-4726-819C-29DC3A2B6CCB@xxxxxxxxxxxxxxxx
Ryan, thanks for your response.

My application is not a problem. Rather I am looking for a best practice
from a MSCS perspective to achieve the following:

1) The ability to monitor the state of multiple instances of the same
application, while only one instance is in an active mode. (Probably using
multiple resource groups).

2) The ability to failover active state. The ability to monitor the state
of
all application instances and make failover decisions based on application
state. (Probably using another resource group and custom code with the
MSCS
eventing mechanism).

So my questions:

Is there a best practice or out of the box mechanism to achieve some / all
of the above.

If a custom solution is required, do you think I am moving towards the
land
of unintended / unsupported.

"Ryan Hanisco" wrote:

Hi RonC,

This will really depend on the application. In most cluster-aware apps,
all
nodes stay running with the app ready to go. On failure, the other takes
over with only the time for the failure detect and session reconnect.

If the app is not built for this, your options may be far fewer.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"RonC" wrote:

Hello:

I am planning to integrate an existing application with MSCS. However,
in a
failover scenario a full application startup will take too long.
Therefore I
am planning to implement a warm standby instance of the application. I
would
like that status of the warm standby instance to be a consideration in
a
failover decision.

Do you have any suggestions on how I might accomplish this with MSCS as
opposed to building a custom cluster aware component?


.

Relevant Pages

  • Re: Client access to file shares
    ... have you checked if the clients get the new, ... (command arp -a) ... > We have a 2 node 2003 cluster and have an issue after failover. ... > automatically reconnect to file shares until between 8-12 minutes. ...
    (microsoft.public.windows.server.clustering)
  • WSE 2.0 vs "normal" WebServices
    ... load balancing and failover as well? ... A furture version maybe must be able to custom authentication. ... For the first version of the application the web services are only ... some of the web services to "foreign" clients. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Is there a best practise to implement a warm standby-solution
    ... I suspected that some of what I need is not provided by MSCS. ... ApplicationX is cluster aware. ... This resource group will failover, ...
    (microsoft.public.windows.server.clustering)
  • hyper-v in mscs
    ... I used the excellent "jose barreto's" site to set up a mscs cluster with ms vm in failover environement with a file server storage. ... It evens works fine when i restarted the active node, save, move, and restore is ok. ...
    (microsoft.public.windows.server.clustering)
  • Re: Is there a best practise to implement a warm standby-solution
    ... Doing all this on a failover cluster is just adding complexity. ... I suspected that some of what I need is not provided by MSCS. ... ApplicationX is cluster aware. ...
    (microsoft.public.windows.server.clustering)