February 23, 2011 at 11:51 am
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?
February 23, 2011 at 10:23 pm
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.
February 23, 2011 at 11:03 pm
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.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply