Timeline for Transaction Log Shipping doesn't use the latest transaction log
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2018 at 19:11 | vote | accept | M Bartolomeo | ||
| May 26, 2014 at 23:18 | comment | added | Kin Shah | @MBartolomeo you have to do some testing on what works in your environment. To be frank, we use log-shipping for all our PROD databases and till today, I didn't have to modify schedules of restore jobs (we run it every 1 mins). Logshipping just works fine. | |
| May 23, 2014 at 23:46 | comment | added | Hannah Vernon♦ | You would need to adjust this offset to accomodate for the approximate time it takes to perform each log backup. | |
| May 23, 2014 at 22:59 | comment | added | M Bartolomeo | Hi there, I did more testing and found a better answer. When you setup the restore schedule on the secondary server, instead of starting the daily schedule at 12:00:00, start it at 12:02:00. SQL calculates this as 17, 32, 47, and 02 of every hour when using 15 minute interval. This way, your secondary database's restore job matches the primary database's backup schedule duration. | |
| May 23, 2014 at 21:27 | history | answered | Kin Shah | CC BY-SA 3.0 |