SQL Server 2008 Logshipping not Restoring
- by Nai
I am getting the following errors during the restore part of the Logshipping process on my secondary server:
2010-04-01 10:00:01.85 Error: The file
'F:\UK_20100327090001.trn'
is too recent to apply to the
secondary database
'UK_Backup'.(Microsoft.SqlServer.Management.LogShipping)
2010-04-01 10:00:01.85 Error: The log in this backup set begins at
LSN 55408000007387500001, which is too
recent to apply to the database. An
earlier log backup that includes LSN
55147000001788900001 can be restored.
RESTORE LOG is terminating
abnormally.(.Net SqlClient Data
Provider)
2010-04-01 10:00:01.87 Searching for an older log
backup file. Secondary Database:
'UK_Backup'
2010-04-01 10:00:01.90 Skipped log backup file.
Secondary DB: 'UK_Backup',
File:
'F:\UK_20100324090000.trn'
2010-04-01 10:00:01.93 Error: Could not find a log backup file that
could be applied to secondary database
'UK_Backup'.(Microsoft.SqlServer.Management.LogShipping)
2010-04-01 10:00:01.93 Deleting old log backup files. Primary
Database: 'UK'
2010-04-01 10:00:01.96 The restore operation
completed with errors. Secondary ID:
'c066bb63-930c-4b73-861c-f59f0a38c12c'
It was happily humming along until I checked it this morning.
Some additional details. In the Logshipping folder, there is one file UK_20100324090001.trn dated on the 2009-3-24. The next most recent .trn file is the UK_20100374090001.trn which is the file that was applied during the restore.
Why is there an older trn file seemingly on it's own?
How can I fix this problem? It'll be a real pain to restart the entire logshipping process. x_x
