Clustering and Automatic Failover Servers

Clustering and Automatic Failover Servers Consulting Services

In the midst of a client request, there is a possibility that the member server the client is trying to access might fail. The ability of the cluster to handle this request is Automatic Failover. If a client has an object reference (IOR) for a component on a server that is a member of a cluster, the client's object reference will be usable, with 100% transparent Failover, unless all the servers in the cluster fail. The primary benefits of automatic Failover are:

• Client code does not have to handle possible server failure
• Provides reliability of component access

For the latest information about Clustering and Automatic Failover Servers

Failover Clustering

Failover clustering is the best solution for simple, quick, and automatic failover. It is the only high-availability solution that provides absolute transactional currency and consistency and makes failover virtually transparent to the client. Consider using failover clustering as your first choice for high availability ahead of log shipping and transactional replication.

For the latest information about Failover Clustering

Failover Clustering Overview

Failover clustering maintains at least one standby server in an MSCS cluster in case the primary data center server fails. Windows 2000 Advanced Server supports two-server clusters, and Windows 2000 Datacenter Server supports up to a four-server cluster. When the MSCS detects that the primary server has failed, it automatically starts the cluster resources on a standby server that were running on the failed server. MSCS then redirects all client traffic to the standby server. You can also manually failover to a standby server. With failover clustering, all committed transactions are always available through the standby server after the primary server fails.

For the latest information about Failover Clustering Overview