SQL SERVER – FIX : ERROR : 4214 BACKUP LOG cannot be performed because there is no current database backup

I recently got following email from one of the reader.

Hi Pinal,

Even thought my database is in full recovery mode when I try to take log backup I am getting following error.

BACKUP LOG cannot be performed because there is no current database backup. (Microsoft.SqlServer.Smo)

How to fix it?

[name and email removed as requested]

backuperror SQL SERVER   FIX : ERROR : 4214 BACKUP LOG cannot be performed because there is no current database backup

Solution / Fix:

This error can happen when you have never taken full backup of your database and you try to attempt to take backup of the log only. Take full backup once and attempt to take log back up. If the name of your database is MyTestDB follow procedure as following.

TO DISK = N'C:\MyTestDB.bak'
TO DISK = N'C:\MyTestDB.bak'

Reference: Pinal Dave (http://blog.SQLAuthority.com)

17 thoughts on “SQL SERVER – FIX : ERROR : 4214 BACKUP LOG cannot be performed because there is no current database backup

  1. Can also happen if you change the recovery model. If you happen to switch from full to simple and back to full (such as for reindexing maybe) then it should immediately followed by a full backup. SQL 2000 used to back up logs with no errors in this situation but the logs will not work if you attempt to restore. SQL 2005 and 08 do error out asking for a full backup.


  2. Hi

    After changing the recovery model also we will get the same error.but when he is trying to take log backup after full backup the recovery model chaged to simple and again moved to simple(here LSN chain was broken).the solution for this to maintain log chain we need to take differential backup it will allow you to take log backups after differential backup.for more inforamation http://www.sqlskills.com/BLOGS/PAUL/category/BackupRestore.aspx



  3. Hi Pinal

    I’m getting the same error message. BUT my backup is present!

    At 2000 I take a full backup of my database (recovery model is set to FULL.)

    Every hour I take a transaction log backup. It works at 2100, 2200 etc until 0600 when it fails with the message
    “BACKUP LOG cannot be performed because there is no current database backup.”

    I checked the backup location – the .bak file is there, as are all my .trn files up to 0500. I haven’t run any truncate jobs.

    I take an ad hoc backup at 0953, and the 1000 log backup works perfectly.

    What am I missing? Does Microsoft have a special definition of “current”?



  4. Ah – found the problem – there *was* a job running to truncate the logs of one of the databases – now disabled, and I expect the problem to go away.


  5. a transaction log backup work between 2 Diffrenshial backup
    you should first run a diffrentioal backup and then run transaction backup,
    have a good time,.


  6. Hi pinal,

    SuperSocket Info: Bind failed on TCP port 1433. what does this error means and how to fix it

    In my server, data is saving in temp database not in .mdf & .ndf thus i need to fix how can fix this issue’s

    Following issues

    1. Invalid Protocol specified for a ?????t?c?????t?????? instance: ???y?????t?c?????t??????.

    2. SuperSocket Info: Bind failed on TCP port 1433.

    3.LogEvent: Failed to report the current event. Operating system error = 31(A device attached to the system is not functioning.).

    Please advise me the solution or how to fix this issues



  7. I have a load job that switches to Bulk-Logging and then back to Full. All that I have found states that this error is when switched to Simple, then back to Full. Does anyone know if this is correct because I have not seen this before with bulk logging to full.


  8. What if the database size is around 200GB. Taking backup first means keep 200GB odd disk space free and then wait for the LOG backup to happen. This definitely is not the option!!! :(


  9. Hi to all,

    If the database is from 2000 want to Restore to 2012 then first restore to 2005 / 2008 then restore to 2012 by unchecking tail-log Backup option.

    The error can be rectified (in MSSQLSERVER2012) and database can be restore by Unchecking the Tail-Log Backup from Options in Restore Database Window.


  10. Dear Deve,
    if I run same below sql backup query
    backup database School to DISK = ‘C:\School_Full_database_Backup.BAK’
    more than one time, why back up file size keep on increasing rather than just overwrite the first file?
    i am using Sql server 2008


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s