Replication Vs Log Shipping Vs Mirroring - Which One Should I Use?

  • Hello,

    I've been looking at the various redundancy/failover technologies within

    SS2008R2 and was wondering which one of the following to use and why or

    where one is preferable to another:

    * Log Shipping

    * Replication

    * Database Mirroring

    If I recall correctly, mirroring is a new addition since SS2005, so is this

    an effective replacement for one or both of the others?

    Any advice as to which to use or any experiences relating to using one over

    the others would be much appreciated.

    Regards

    Steve

  • Well it all depends on your RTO and RTP as to which to choose and if you want hot, warm or cold standbys.

    If you know this information then you can choose between, clustering, replication, logshipping, mirroring.

    If you ever plan to go to SQL 2012, mirroring is a depreciated feature, and has been replaced by Always On Availability Groups.

  • Hello,

    RTO? ... RTP?

    OK, this is all a bit new to me, so I apologise for my ignorance. I am studying SQL and trying to get to grips with its various features.

    I have two PC's and wanted some pointers to perhaps summarize the various advantages and disadvantages of each technology.

    As someone new to SQL Server (coming from a 3GL background) I find the deprication of sometimes long standing facilities a nightmare to try and cater for as far as development is concerned.

    ANy further help you might be able to offer would be greatly appreciated.

    Regards

    Steve

  • RTO = Recovery time objective - How long do you have to recover service?

    RTP = Recovery time point - How much data can you afford to loose?

    If a server dies and you need to have it back online in 5 minutes with minimal data loss your looking at clustering or mirroring.

    Typically we use a 3 tier setup.

    2 servers in primary data centre, 1 server in secondary data centre.

    Between the primary servers we have clustering in place and to the secondary we have logshipping.

    This is down to the fact that we would not want to fail over the whole IT systems for one server outage, and the latency between primary and secondary was to much for mirroring.

    Our RTP is 15 minutes, so logshipping is setup to run every 15 minutes, and in the event that something should go wrong, our RTO is 4 hours, so we have 4 hours to get service restored.

    This link might help you on the right tracks

    http://www.sqlservercentral.com/blogs/databaseexpertisecom/2010/08/12/different-high-availability-solutions-in-sql-server-_1320_-by-abi-chapagai/

  • Thanks so much for your time helping me with all this.

    I will take a look at the link you kindly provided.

    If I may ask, seeing as you're using mirroring between your two primary data center servers, will you elect not to upgrade to SS2012 in view of this feature being depricated?

  • anthony.green (8/9/2012)


    RTO = Recovery time objective - How long do you have to recover service?

    RTP = Recovery time point - How much data can you afford to loose?

    Weird, I always called them

    RTO = Recovery Time Objective

    and

    RPO = Recovery Point Objective

    Would be interesting to know which one is more correct or, at least widespread. Since I'm not English nor American I would really like to know and possibily correct myself.

    -- Gianluca Sartori

  • Yep it is RPO, dont know where I got RTP from, must be a combination of RTO and RPO.

  • anthony.green (8/9/2012)


    Yep it is RPO, dont know where I got RTP from, must be a combination of RTO and RPO.

    Ah, great. Thanks Anthony.

    -- Gianluca Sartori

  • MIRRORING feature not depricated in SS2012 instead it is enhanced as Always On

  • prasantiki (7/27/2014)


    MIRRORING feature not depricated in SS2012 instead it is enhanced as Always On

    Mirroring is deprecated. Availability Groups is a new feature, not a direct upgrade (it's a mix of clustering and mirroring and has limitations that mirroring doesn't), it's Enterprise-only where as Mirroring was Standard and Enterprise.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply