Andrew Cruz-Moores (7/23/2012)
I have log shipping configured between a primary and secondary server. The secondary server will not restore files if they are not in the files name is not in the format of DBNAME_YYYYMMDDNNNNNN.trn where NNNNNN is some sort of sequence number. The files that are being skipped are in the format DBNAME_Backup_YYYY_MM_DD_HHMMSS.trn. The files have valid transations in them meaning the LSNs are in the correct order.
NNNNNN is not a sequence number. It's a timestamp of a sort. Look at it as military hours, minutes, seconds.
Why is the restore job skipping files NOT following the naming convention DBNAME_YYYYMMDDNNNNNN.trn?
Because those other backups are not in the same backup log chain as the ones being used by the log shipping. The first naming convention is used by automated SQL Server backups created through the maintenance plan or third party SQL backup tools like Litespeed.
The second naming convention smacks of a backup plan manually scripted out in T-SQL then run as a job or run through the GUI. Hence those backups are not in the same backup / restore chain as the others.
EDIT: FYI, You are making a huge (and incorrect) assumption about valid transactions and LSNs. The two have nothing to do with each other.
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.