Ravi-156610 (12/6/2012)
We have Log Shipping setup on SQL 2008 instances and everything was running fine until the primary database was accidentally taken offline. We bought the DB online but noticed that the Log Shipping restore was failing. All the logs that were generated after the primary DB state change (offline\online) were not being restored on the secondary DB.Does the database state change break the Log Shipping setup? How different would a database state change be from an instance restart?
Thanks,
Ravi
how long was log shipping down for?
Where the Log shipping jobs interrupted?
What does the history show for the copy and restore jobs on the secondary instance?
In most cases you can take a differential backup of the primary and apply to the secondary to resume log shipping. This will only be possible if there has been no full backup on the primary since the last successful secondary restore.
Check using this query against the primary and secondary to see if the differential base LSNs are synchronised
select DB_NAME(database_id), differential_base_lsn
from sys.master_files
where database_id = DB_ID('yourLSdb')
group by differential_base_lsn, database_id
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉