May 4, 2010 at 12:57 am
My restore failed with the error: backup begins at LSN which is too recent to apply.
On checking backup history: i have the following backups taken:
Missing LSN backup 2:30 AM - Tlog
backup2 10:30 PM - Tlog
FUll backup 10:45 PM - Full
Backup 4 11:00 PM - Tlog
backup 5 11:30 PM - Tlog - MOST current backup
Since there is a full backup in between the missing lsn and current backup, i feel taking a full backup and restoring is the best possible way.
Please let me know if I am correct?
May 4, 2010 at 1:50 am
sqlwars (5/4/2010)
My restore failed with the error: backup begins at LSN which is too recent to apply.On checking backup history: i have the following backups taken:
Missing LSN backup 2:30 AM - Tlog
backup2 10:30 PM - Tlog
FUll backup 10:45 PM - Full
Backup 4 11:00 PM - Tlog
backup 5 11:30 PM - Tlog - MOST current backup
Since there is a full backup in between the missing lsn and current backup, i feel taking a full backup and restoring is the best possible way.
Please let me know if I am correct?
restoration needs some sequence. refer this link
http://www.databasejournal.com/features/mssql/article.php/3591131/COPYONLY-Backups-in-SQL-Server-2005.htm it might help you.
Additionally what you are getting with
select message_id, severity, [text] from sys.messages where language_id = 1033 and severity <> 10 and [text] like ‘%backup%’
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
May 4, 2010 at 1:53 am
With the backups that you list, you can restore using the full backup and the last 2 transaction log backups. What happened to the file from the log backup at 2:30?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 5, 2010 at 2:54 am
gave teh detailed explanation and cleared few myths too!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply