I've read a lot of the information about this topic in MSDN. My boss askme to understand and to let working an example application of Cluster Mirroring. The problem is that i dont understand well yet what is a Cluster and what is the main idea behind it.
If someone really understand and can explain me clearly whats behind it, i will be very grateful. Thanks a lot for the help. ( Sorry for me english :( )
Ok, Basically a cluster is a two-headed monster. Chop one of it's heads off and nothing will happen, it will still carry on chasing you.
In computer terms, the simplest cluster is a two-node cluster (two headed monster) , two physical computers sharing the same name and IP address. If one of the computers making up the cluster fails (chop one head off) the cluster will still carry on functioning (chasing you) on the other computer participating in the cluster.
The general idea behind it is to provide high-availability for your apps by eliminating a single point of failure.
|||
Thanks bobbins!
But i have another question ... when you have a mirror database with a witness, you also provide high-availability. Because if something happen the mirror will continue chasing you .. Why is much better the cluster ? Thanks a lot again
|||There are many discussions/articles on Clustering vs Mirroring vs Replication vs Log Shipping
In short, I think clustering is still a better solution for high-availability, PROVIDED that you do have a SAN
We're using mirroring now until we can get a SAN in, then we'll move to clustering
sqlsql
No comments:
Post a Comment