Hello there,
I set up Log Shipping and all was working fine till this morning when I queried the secondary db to see if the DB is is sync with the primary Db and it turned out that since 21th Sept, the secondary DB is not getting updated.Under LSAlert job report in primary & secondary server the status shows 'Alert' in red whereas the copy & restore jobs are running properly.Also the share folders, I see all the files with the correct dates. but the secondary db is not in sync. One thing to mention is that the 2 servers time has gone 1 hour back since 22 Sept due to Daylight saving. Could that have messed the log shipping. Now what is the way out to this. Do i need to del the log shipping which I created and again create a new one again.Please help!!!!
cheers
Zolf
it can be due to size of your prim DB trans log size\network slowness..delay)
and if your Secondary DB is out of sync for long time due to corrupted trans log file
you may need to reinit log ship ...
before you start reinit:
please check for the issues that sounds like corrupted trans log backup file that you may got by rebooting server during trans log backup ( as an example)
check:
Different ways to monitor Log Shipping for SQL Server databases
https://www.mssqltips.com/sqlservertip/2553/different-ways-to-monitor-log-shipping-for-sql-server-databases/