June 18, 2013 at 10:46 am
I have a vendor's production MicroTel.
It has 3 databases. They are all at bulk-logged recovery mode.
I setup a maintenanance plan to do full at weekend and every day a differential, and every 3 hours a transaction log backup.
I got a failed error:
BACKUP LOG cannot be performed because there is no current database backup.
I do see it has a full backup and a differential before the transaction log backup, why it said no current backup?
I can also verify it has a full backup by using restore the database from SSMS, I see it listed the most recent full back up and differential backup.
THanks,
June 18, 2013 at 11:10 am
Someone's run a switch to simple recovery and back to full since the last full/diff backup. It'll be logged in the error log.
p.s. Are you sure you want those DBs in bulk-logged recovery all the time?
http://www.sqlservercentral.com/articles/Recovery+Model/89664/
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
June 18, 2013 at 11:19 am
Thanks that is what I suspected too.
But I did a readerror_log 'recovery' and found that was a week ago.
The change is a bulk-logged backup.
But the full backup is on most recent sunday.
June 18, 2013 at 11:26 am
Either the database was switched to simple recovery or the log was truncated explicitly (which isn't possible on SQL 2008) or the database was reverted to a snapshot. That's about the only things that will break the log chain and have SQL know about it.
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply