March 31, 2017 at 9:35 am
Hi Guys,
I have two questions. I just restored a full backup into norecovery from a SQL Server 2008R2 onto a SQL Server 2016. Successfully.
I then took a DIFF of the source and tried to restore that and it failed with the following error:
Msg 3136, Level 16, State 1, Line 40
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 40
RESTORE DATABASE is terminating abnormally.
Normally I would accept that another full backup was somehow taken in between but I know this not to be the case.
Is there a way with the backup files (full and diff) to identify if they 'belong with each other'
Or, failing that am I wrong in my assumption the problem is log-chain related? How can I find out what the correct earlier state means in this case?
Cheers
Alex
March 31, 2017 at 9:42 am
alex.sqldba - Friday, March 31, 2017 9:35 AMHi Guys,I have two questions. I just restored a full backup into norecovery from a SQL Server 2008R2 onto a SQL Server 2016. Successfully.
I then took a DIFF of the source and tried to restore that and it failed with the following error:
Msg 3136, Level 16, State 1, Line 40
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 40
RESTORE DATABASE is terminating abnormally.Normally I would accept that another full backup was somehow taken in between but I know this not to be the case.
Is there a way with the backup files (full and diff) to identify if they 'belong with each other'Or, failing that am I wrong in my assumption the problem is log-chain related? How can I find out what the correct earlier state means in this case?
Cheers
Alex
what is the recovery model of the source db?
😎
March 31, 2017 at 9:47 am
Good point, it is being log shipped too... But I just double checked to rule out any crazy and can confirm its FULL.
It is in 2005 Compatibility Mode. Related?
March 31, 2017 at 12:33 pm
So looking through backupset and backupmediafamily has highlighted the naughty person who forgot to add 'copy_only' when doing an adhoc commvault backup!
He has been ridiculed and taunted.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply