January 26, 2012 at 6:02 am
I restored a Database in Standby Mode.
I attempt to restore the differential with recovery and I get the the following error:
Msg 3136, Level 16, State 1, Line 1
This differential backup cannot be restored because the database has not been restored to the correct earlier state.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I assume that I can't do that?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 26, 2012 at 6:48 am
Which backup sets did you restore?
FULL + DIFF only? No TLOG?
-- Gianluca Sartori
January 26, 2012 at 6:53 am
Are you absolutely sure that the differential you have is based off the full backup that you restored? There were no other full backups taken between the time that full backup was taken and the differential backup was taken?
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
January 26, 2012 at 7:01 am
GilaMonster (1/26/2012)
Are you absolutely sure that the differential you have is based off the full backup that you restored? There were no other full backups taken between the time that full backup was taken and the differential backup was taken?
I thought the same thing but I'm positive that there were no other full backups.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 26, 2012 at 7:14 am
The error implies there were. Did you check MSDB backup tables? Did you check the LSNs in the full and diff backup headers?
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
January 26, 2012 at 7:41 am
GilaMonster (1/26/2012)
The error implies there were. Did you check MSDB backup tables? Did you check the LSNs in the full and diff backup headers?
I'm sure that is what happened but I did not do a Full Backup since the one that I copied.
I checked the MSDB BackupFile and the others. How do I tell what is the most recent?
What do I look for in the LSN's?
Thank you.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 26, 2012 at 7:46 am
Welsh Corgi (1/26/2012)
GilaMonster (1/26/2012)
The error implies there were. Did you check MSDB backup tables? Did you check the LSNs in the full and diff backup headers?I'm sure that is what happened but I did not do a Full Backup since the one that I copied.
Did anyone else? Any automated backups?
I checked the MSDB BackupFile and the others. How do I tell what is the most recent?
Err, well you know which full you copied and which diff you copied from the file names and the dates they were taken, so check that there weren't any other full backups between (you may need to join a few tables)
What do I look for in the LSN's?
That the differential's base LSN matches that of the full backup.
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
January 26, 2012 at 7:50 am
use below query
select database_name, type, first_lsn, last_lsn ,checkpoint_lsn ,database_backup_lsn
from msdb..backupset where database_name = 'DBNAme'
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply