Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

BACKUP LOG cannot be performed because there is no current database backup. Expand / Collapse
Author
Message
Posted Tuesday, June 18, 2013 10:46 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 9:54 AM
Points: 1,720, Visits: 3,063
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,
Post #1464788
Posted Tuesday, June 18, 2013 11:10 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 41,508, Visits: 34,424
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1464797
Posted Tuesday, June 18, 2013 11:19 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 9:54 AM
Points: 1,720, Visits: 3,063
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.
Post #1464801
Posted Tuesday, June 18, 2013 11:26 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 41,508, Visits: 34,424
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1464805
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse