SQL Server Log Shipping Does Not Replace Replication

By Zerto, on 16 January, 2014

SQLProtecting databases is challenging as transactions are written quickly and there is a high rate of change within the application. Many organizations use log shipping as a recovery method, which typically translates to a manual recovery process and overall higher risk. In addition to this complexity, just getting the data to the recovery site is insufficient as the order of the I/O is critical for database recovery. If write-order fidelity is not preserved, the database cannot be recovered without additional manual intervention.

Log shipping is used between two copies of a single database that are housed on different computers. Updates made to the primary database are shipped to the secondary database. The transaction log from every insertion, update, or deletion made on the primary database gets applied onto the secondary database.

So what happens in case of a disaster? According to this article from a popular DBA blog, “In a disaster where the primary server cannot be restarted because of a power grid failure, you may stitch the primary server’s active transaction log and transaction log files together by using a third-party transaction log analyzer to identify transactions that did not make it across and manually apply them.” Basically, piecing your database applications back together after an outage is going to be painstakingly manual. [Read more about this in our Recovery for Microsoft SQL Data Sheet]

Zerto is excited to invite Uzah Chinedu, the Infrastructure Manager at Leadway Pensure PFA Limited to our “Hear from your Peers” webinar series. Leadway relies heavily on Microsoft SQL Server. Mr. Chinedu struggled to locate a solution which would keep up with the high rate of change of SQL Server. He had evaluated several solutions, but none of them maintained the write-order fidelity of the application. With Zerto Virtual Replication, Mr. Chinedu can maintain the integrity of his database when replicating. Additionally, seamless testing provides a new level of confidence throughout the organization in terms of the ability to recover quickly from an outage.

Join the webinar on February 4, 2014 to hear from Uzah and learn about simple, effective SQL recovery with Zerto.

Register Button

 

0 comments on “SQL Server Log Shipping Does Not Replace Replication

Leave a Reply

Your email address will not be published. Required fields are marked *


*