August 3, 2013 at 9:19 am
Ok, so here's the issue. We have a report server database that has been correctly been updating tlogs for years. A couple days ago, we shrunk the live database/log, and now we continue to receive "gaps" in the tlogs. Does anyone have any suggestions on how to resolve this? Should we somehow restore the entire report server database with the live database...and the tlog shipping will just kick in from there??
August 3, 2013 at 2:25 pm
What do you mean by 'gaps in the tlogs'?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 3, 2013 at 2:43 pm
how did you shrink the log, what commands did you issue?
Are you saying log shipping is now broken due to missing lsns?
If so and you have not issued a full backup of the live database since the log truncate you can restart log shipping using a differential backup, else you will need to restore the secondary from a full backup (with norecovery), log shipping will then pick up again.
---------------------------------------------------------------------
August 3, 2013 at 3:04 pm
You hit the nail on the head. I ended up taking the full backup of the live DB (that occurred last night), restoring it to the report server DB, then restoring the log files up to the present. All seems good now! I'll keep an eye on it.
FYI: For me, the real secret was to RESTORE WITH STANDBY!!
August 3, 2013 at 3:09 pm
j2cagle (8/3/2013)
You hit the nail on the head. I ended up taking the full backup of the live DB (that occurred last night), restoring it to the report server DB, then restoring the log files up to the present. All seems good now! I'll keep an eye on it.FYI: For me, the real secret was to RESTORE WITH STANDBY!!
thought I might have, The first log restore run via the log shipping jobs would have put the database into whatever mode you had set before (restoring or standby mode).
---------------------------------------------------------------------
August 3, 2013 at 3:16 pm
george sibbald (8/3/2013)
The first log restore run via the log shipping jobs would have put the database into whatever mode you had set before (restoring or standby mode).
I was thinking that it would do that, but I was impatient so forced it myself...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply