SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Can't restore the log


Can't restore the log

Author
Message
sql2004
sql2004
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 7
I'm backup the database using a job. Backup one filegroup per step. The last step is a transaction backup.

When I'm trying to restore the log backup got following error:
"The log in this backup set begins at LSN 188485000000009400255, which is too recent to apply to the database. An earlier log backup that includes LSN 188485000000007400001 can be restored."

I verified the order of the backup and is the same of the restore but I think the log backup is very close to the last filegroup backup.

I compre the lsn using restore header. The first lsn of the transaction log backup is in the range of the last filegroup backup and the last lsn of the log backup is grater than the last lsn of the last filegroup backup.

Anyone have an idea to restore the log backup?



John.Liu
John.Liu
SSC Eights!
SSC Eights! (820 reputation)SSC Eights! (820 reputation)SSC Eights! (820 reputation)SSC Eights! (820 reputation)SSC Eights! (820 reputation)SSC Eights! (820 reputation)SSC Eights! (820 reputation)SSC Eights! (820 reputation)

Group: General Forum Members
Points: 820 Visits: 370
The error indicates an earlier log backup needs to be restored first. Is there any other tlog backup happending on the server before your last tlog backup? Have a look in MSDB of the backup history of your db for the period between your first filegroup backup and your last tlog backup. Also, if you can, post the backup file header info in your restore sequence.
Ray Mond
Ray Mond
SSCrazy
SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)SSCrazy (2.8K reputation)

Group: General Forum Members
Points: 2805 Visits: 1544
I compre the lsn using restore header. The first lsn of the transaction log backup is in the range of the last filegroup backup and the last lsn of the log backup is grater than the last lsn of the last filegroup backup.

The first lsn of the trx log backup should be in the range of the first filegroup backup, as only then will it contain all changes made to that filegroup and all other filegroups until the last filegroup has been backed up.

As suggested by John, checking the backup history tables should tell you if another trx log backup was taken before the one made by your job.

SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search