Friday, November 18, 2011

Log Shipping VS Mirroring

With Log Shipping:


Data Transfer:    T-Logs are backed up and transferred to secondary server
Transactional Consistency:  All committed and un-committed are transferred
Server Limitation:   Can be applied to multiple stand-by servers
Failover:   Manual
Failover Duration:  Can take more than 30 mins
Role Change:   Role change is manual
Client Re-direction:  Manual changes required

With Database Mirroring:

Data Transfer:    Individual T-Log records are transferred using TCP endpoints
Transactional Consistency:  Only committed transactions are transferred
Server Limitation:   Can be applied to only one mirror server
Failover:   Automatic
Failover Duration:  Failover is fast, sometimes < 3 seconds but not more than 10 seconds
Role Change:   Role change is fully automatic
Client Re-direction:  Fully automatic as it uses .NET 2.0

1 comment:

  1. Just adding.

    Database Mirroring
    ------------------
    Fail over :It is both way i,e Automatic or Manual -it depends on what mode we will select in the configuration of Database mirroring.

    Log Shipping
    ------------
    Failover Duration: Can take more than 30 mins

    ---This will depends on how We(DBA) will work in case of issue arises when you are doing fail over to secondary database because even though it seems easy to do the fail over in log shipping, but if the issues arises when you are actually performing then it depends(how quickly you will resolve).

    There are many differences b/w log shipping & mirroring pointing out it's own advantage/disadvantages.



    Best Regards,
    Rama Udaya.K
    ramaudaya.blogspot.com

    ReplyDelete