Log Shipping

Question

Log Shipping

aby_dvd

Ten Centuries

Points: 1310
More actions
January 27, 2012 at 3:08 am

#254422

What is the t log files get corrupt in a log shipping setup ?
What are we DBA's supposed to do then to perform the restore in the secondary server ?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

arr.nagaraj SSCertifiable Points: 6528 More actions · Answer 1

You mean on the sceondary you have disk level corruption on the log file?

if thats the case , make sure the storage errors are fixed and and then try to restore using the lastt full backup + recent t-log backups that were created in the log shipping shared folder.

Regards,
Raj

http://Strictlysql.blogspot.com

umasingh Ten Centuries Points: 1182 More actions · Answer 2

Is there any specific error you are seeing in logshipping monitor or in error log?

Brandie Tarvin SSC Guru Points: 173045 More actions · Answer 3

If the log files are corrupted, chances are that they are corrupted when they are being taken, not when they are being received on the log shipping side.

But this is something you should test. Before you touch the log server, try restoring the latest full backup + all transaction logs taken after that to a sandbox server or as another database name. If they restore fine, then the corruption is happening on the log shipping server media. If they do not restore fine, you have a bigger problem.

In addition to fixing the destination server, you will need to track down the cause of the corruption (whether it is a bad file / filegroup / extent or a bad disk drive) and fix that in order to prevent further problems and a loss of all data.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

MyDoggieJessie SSC-Forever Points: 44486 More actions · Answer 4

I would reccommend checking your Agent job (LS_RESTORExxxx) and see if you can track down when the errors began, it should tell you which TRN file started causing the problem, and of course, redoing log shipping on a test server or as a different DB name (as Brandie suggested) will most likely tell you the same thing, if you have the time to do that.

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

SQlLogic SSCrazy Eights Points: 9686 More actions · Answer 5

If the sequence of Transaction log is broken due to a corrupted log file, then in order to get the sequence back you must restore the complete database backup from primary server to the secondary server.