SQL SERVER – Fix : Error Msg 4214 – Error Msg 3013 – BACKUP LOG cannot be performed because there is no current database backup

This is very interesting error as I could not found any documentation on-line. It took me nearly 1 hour to figure out what was creating error.

Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.

Reason :
This error happened when we were truncating the logs before we take backup of the database.

Fix/Workaround/Solution :
Do not truncate log if differential backup is set up. Truncating log before backup brakes continuity of the log and creates issues when they are to be restored. Disrupted continuity creates not useful back up. This errors warns user when backup are becoming worthless.

Transactional backup truncates the log itself so there is no need to truncate log to keep it maintained.

Reference : Pinal Dave (https://blog.sqlauthority.com)

SQL Backup and Restore, SQL Error Messages, SQL Scripts, SQL Server
Previous Post
SQL SERVER – 2005 – SSMS – View/Send Query Results to Text/Grid/Files
Next Post
SQL SERVER – Fix : Error Msg 1813, Level 16, State 2, Line 1 Could not open new database ‘yourdatabasename’. CREATE DATABASE is aborted.

Related Posts

3 Comments. Leave new

  • I am having the problem described above. I have not truncated logs, but I am still having this problem. There are multiple databases on the same server, only one of them is having this issue.

    Since I am not truncating logs, how can I fix this?

    May 22, 2008 10:22 am

    It may be because u have been taken the backup (full) in simple recovery model, than u changed it to full revery mode, and took the Trn log backup…..

    if u have changed the recovery model from simple to Full than first u have to take full or differential backup…than u have to take trn log backup….


    Virendar Singh

  • RE the statement: “Transactional backup truncates the log itself so there is no need to truncate log to keep it maintained.”

    Can you elaborate on this or point to some reference that explains how to keep a log file maintained at minimum size with DBA tools and practices, and in a manner that takes advantage of enterprise backup tools?

    We have both SS2200 and 2005 running on several servers, two clusters, and dozens of large databases that for some reason generate large t-logs (50 – 100 GB per server). It has become a very frequent occurrence that the log storage devices, SAN disks, become full. Now, we have Legato (for SS2000) and Microsoft DPM (for SS2005) running to do a full back up of all databases every night. So if I am to “maintain” these large log files, I don’t want to attempt to backup the databases to disk, that would be redundant and consume the very space I’m trying to free up.

    Is there a sensible way to “maintain” log files that grow to large sizes? BTW some of these log files belong to databases such as Changepoint and MOM, i.e. Microsoft products…


Leave a ReplyCancel reply

Exit mobile version