Using Log Shipping With Delayed Recovery

Kenneth Igiri shows how you can combine log shipping with delayed recovery to prevent data loss due to user mistakes:

Now let’s talk about the key benefit of this delay. In the scenario, where a user inadvertently drops a table, we can recover the data quickly from the Secondary Database as long as the Delay period has not elapsed. In this example, we drop the table Sales.Orderlines on BOTH databases and verify that the table no longer exists in BOTH databases.

It’s a fairly expensive technique but potentially still cheaper than restoring from backups.

Related Posts

Log Shipping Tests With dbachecks

Sander Stad has a bonus post in his log shipping series: We want everyone to know about this module. Chrissy LeMaire reached out to me and asked if I could write some tests for the log shipping part and I did. Because I wrote the log shipping commands for dbatools I was excited about creating […]

Read More

Recovering A Log-Shipped Database

Sander Stad wraps up his series on log shipping: Initially log shipping was meant to be used as a warm standby. You have your data on another instance but you still have some human intervention to get it all back up. Imagine the following situation. You have setup log shipping using either the GUI or […]

Read More

Categories

August 2018
MTWTFSS
« Jul Sep »
 12345
6789101112
13141516171819
20212223242526
2728293031