High Availibility
Working with Cluster Group in Windows Server 2008
Windows 2008 failover cluster administrator is difficult to figure out. To failover to another node, you can use the UI or use the command line. The UI is easy as you can see in this image:
However, you can move the Cluster Group by using command line as follows
cluster group "cluster group" /move:sgjssdlvmrd057
Next, to get the cluster configuration of the quorum
Memcache equivalent product by Microsoft
Microsoft is coming out with a competitive product to Memcache, one of the most popular data caching products on linux. It looks like it will be free also and available this summer.
Are clustered servers too difficult?
I was talking with my friend the other day who works for a medical device manufacturer about his companies fear of clustered servers. His peers and managers have the opinion that clustered servers are hard to maintain, including long a frequent maintenance periods and are difficult to support.
Active-Active Clusters, should you use them over Active-Passive?
I have commonly worked with companies that use active-passive clusters for high-availability. Clustering is a good idea, but with active-passive clusters, one cluster is sitting idley waiting for failure of the other server. This is an expensive proposition in typical enterprise environments. This is not true in active-active clusters.
In an active-active cluster, both servers are in use. They provide hardware and OS failover for eachother. Clustering is at the server and OS level and doesn't provide data redundancy, just server redundancy.
