Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have several Tb databases in the Windows Server 2008. I would like to keep alive the service when the server is failing or the raids are needs to be rebuild.

Which model to choose Replication or Mirroring? And how to setup that the alive server will takeover the dead one?

Thans Arman.

share|improve this question
add comment

2 Answers 2

up vote 2 down vote accepted

Mirroring that is set up in high-safety mode with the presence of a witness can allow for a switch of the active database instance in a way that is seamless to the application. The catch is that it's a synchronous operation every time there's a transaction... meaning it must be committed on both nodes before the transaction is complete. Therefore, there is increased latency.

With replication, the application has to be aware and be ready to do the switch if it detects a node not up. This is not automatic and definitely not seamless to the application. However, you don't have the transaction latency because it's not synchronous (changes are replicated as soon as possible but not confirmed across all nodes before the transaction is committed).

share|improve this answer
    
Thanks, i did some tests, the replifation is better solution than mirror. If i enable mirroring for db with 5Tb data, it create about 1.5Tb logfiles, mirroring syncronisation goes abot 10hours... I did not test it with partitioned table ,it is in my todo lists:-) . –  Arman Feb 26 '11 at 11:50
add comment

Ah now that is the ultimate question! You will get 101 responses no doubt but if your question is actually asking which of these technologies is probably best suited to making a database available then I would go for Mirroring every single time. Replication is fantastic for scaling of data, and improving availability of subsets of data.

If your question is what infrastructure can I put in place to aim towards 5 nines or better availability then I would start talking about Clustering, Virtualization and Peer to peer replication (last I'd only go for in SQL 2008 R2).

Going back to the Mirroring, for automatic failover you will need a witness server and your server name resolution will need to be addressed (one solution is that you can use failover partner in connection string).

See URL Database Mirroring

share|improve this answer
    
Nice, can I start mirror process on active database, or I should detach all users... –  Arman Feb 24 '11 at 14:17
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.