August 22, 2012 at 7:56 am
Hi, I'm testing log shipping and I have a big doubt. Let's imagine that log shipping jobs are scheduled with 5 minutes interval (for example, backup job at 00.00, copy job at 00.05 and restore job at 00.10, assuming that the database contains few records and only few modify are performed, so every job can complete before the next one starts). In the mentioned example, what happens to records modified between 00.00 and 00.10? The "snapshot" of the primary database has timestamp "00.00" so at 00.11, after restore job, primary and secondary database will not be identical. Am I thinking wrong? 🙁
August 24, 2012 at 9:22 pm
The secondary DB will be 00.00 since that was the log file that was restored from the primary log backup. Secondary will always be behind primary and since the secondary is at best read-only the only time it changes is when you restore a t-log backup from the primary.
---------------------------------------------------------------
Mike Hahn - MCSomething someday:-)
Right way to ask for help!!
http://www.sqlservercentral.com/articles/Best+Practices/61537/
I post so I can see my avatar :hehe:
I want a personal webpage 😎
I want to win the lotto 😀
I want a gf like Tiffa :w00t: Oh wait I'm married!:-D
August 24, 2012 at 9:32 pm
Regarding what happens to data from 00.00 to 00.10 depends on your backup timeframe... if u backup every 5 minutes then you'll have a t-log backup file @ 00.05 and 00.10.... each file will need to be copied and restored to your secondary.. the quicker you do it the more in synch your 2nd is to your primary.
---------------------------------------------------------------
Mike Hahn - MCSomething someday:-)
Right way to ask for help!!
http://www.sqlservercentral.com/articles/Best+Practices/61537/
I post so I can see my avatar :hehe:
I want a personal webpage 😎
I want to win the lotto 😀
I want a gf like Tiffa :w00t: Oh wait I'm married!:-D
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply