Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Insight into a restore problem with Transaction Logs

Status
Not open for further replies.
Sep 27, 2001
179
AU
Hi

When trying to restore a backup I recieved the error:

The log in this backup set begins at LSN %.*ls, which is too late to apply to the database. An earlier log backup that includes LSN %.*ls can be restored.

I did plenty of hunting around on the MS kbase and followed an article ( which should 'determine the earliest log that is required to recover with the latest set of file group backups'

This made reference to a backup that dated back to 2003.

What had happend is that the location of the backups ran out of disk space and although a complete backup should happen everynight it hadn't for a couple of days. I managed to restore without getting the error by de-selecting a couple of the last TRN files.

So, I would like to know why the above query from the kbase article references a file from 2003. Why does it go so far back? I would have thought that it would have take a reference point from the last full backup, which was 13th Aug 2004. These oldcer files have been removed from the system.

Finally, I am assuming that there is no way to retrieve the last two TRN files?

Thanks

Rob Colborne
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top