I tried setting up log shipping less than 24 hours ago and set the backups for every hour. When I look at the history of the agent job on the Secondary server I see a lot of these:
2015-08-26 15:25:05.73 Skipped log backup file. Secondary DB: 'SFIDataLS', File: '\\VSQL3\SFIDataLSBackup\log\SFIData_20150826181000.trn'
Looks like it tries every log that was copied to the share. The next to last entry in the history log is:
2015-08-26 15:25:06.03 Skipped log backup file. Secondary DB: 'SFIDataLS', File: '\\VSQL3\SFIDataLSBackup\log\SFIData_20150826191000.trn'
2015-08-26 15:25:06.03 Could not find a log backup file that could be applied to secondary database 'SFIDataLS'.
2015-08-26 15:25:06.03 The restore operation was successful. Secondary Database: 'SFIDataLS', Number of log backup files restored: 0
2015-08-26 15:25:06.03 Deleting old log backup files. Primary Database: 'SFIData'
2015-08-26 15:25:06.04 The restore operation was successful. Secondary ID: '196ba8d9-a5f5-4632-9091-d3f4a5e3501c'
2015-08-26 15:25:06.05 ----- END OF TRANSACTION LOG RESTORE -----
Exit Status: 0 (Success)
When I try to restore the oldest file in the share from SSMS, I get:
"Restore failed for server VSQL3....
System.Data.SqlClient.SqlError: The log in this backup set begins with LSN ....578340001, which is too recent to apply to the database. An earlier log backup that includes LSN ......4432500001 can be restored.
Does this mean I'm scrapping this and starting over? I can see the dates and times on the logs, so I know when they are taken. I've read before how to relate the LSN to the log, but I don't know if I have a log.
Sunnyland Farms, Inc.
"We must endeavor to persevere."