SQLServerCentral.com / Backups / SQL Server 7,2000 / Backup Log cannot be performed because there is no current database backup / Latest PostsInstantForum.NET v2.9.0SQLServerCentral.comhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 02 Aug 2015 16:28:25 GMT20RE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxThis is very simple step.1. Take the full backup.2. Take the log backup.your problem will resolve.Tue, 28 Jul 2015 10:23:05 GMTBadelal YadavRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxI completely agree with you. I am not sure why they did that to begin with I will create a new optimization job later, but for right now I have to stop it because I need those Tran jobs to run. It's critical!Mon, 08 Apr 2013 07:51:19 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxSo the full backup is reinitialising the log chain and hence the log backups run. It's not a good maintenance schedule though. Switching to simple recovery for index rebuilds is not going to do good things to your ability to restore to a point in time (which I assume is why the DB is in full recovery).Mon, 08 Apr 2013 07:46:12 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxIf we look at the job schedule in terms of yesterday and today. The job to optimize runs at about 8pm 04/07/2013, at the end it returns them to full. Then a full runs about 12 am which will be this morning 4/8. Then the Trans_log runs at 7 am 4/8Mon, 08 Apr 2013 07:31:34 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxTiming of the full backups? Those other databases having diff backups running after the 'optimisation' job?Mon, 08 Apr 2013 07:24:03 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxSo I found the issue. Apparently the previous DBA has a job that is changing the database from Full to Simple to do a database optimization. I don't understand why the previous database did that, but what is more confusing is that all of the other databases are going through the same process and they are not being affected. What gives?Mon, 08 Apr 2013 07:15:57 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspx[quote][b]GilaMonster (4/6/2013)[/b][hr]Since we're going nowhere fast here...Finish this script (the file name) and then run this trace for a couple of days. It will pick up all backups, all restores and all changes of recovery model. After a couple days, open up the trace output in profiler, see what else is taking full backups, if there are any log backups that explicitly truncate the log and if there are any changes in recovery model.[code="sql"]/****************************************************//* Created by: SQL Server 2008 R2 Profiler *//* Date: 2013/04/06 17:18:38 *//****************************************************/-- Create a Queuedeclare @rc intdeclare @TraceID intdeclare @maxfilesize bigintset @maxfilesize = 100;exec @rc = sp_trace_create @TraceID output, 0, N'InsertFileNameHere', @maxfilesize, NULL if (@rc != 0) goto error-- Client side File and Table cannot be scripted-- Set the eventsdeclare @on bitset @on = 1exec sp_trace_setevent @TraceID, 115, 1, @onexec sp_trace_setevent @TraceID, 115, 6, @onexec sp_trace_setevent @TraceID, 115, 10, @onexec sp_trace_setevent @TraceID, 115, 14, @onexec sp_trace_setevent @TraceID, 115, 11, @onexec sp_trace_setevent @TraceID, 115, 12, @onexec sp_trace_setevent @TraceID, 128, 1, @onexec sp_trace_setevent @TraceID, 128, 6, @onexec sp_trace_setevent @TraceID, 128, 10, @onexec sp_trace_setevent @TraceID, 128, 14, @onexec sp_trace_setevent @TraceID, 128, 11, @onexec sp_trace_setevent @TraceID, 128, 12, @on-- Set the Filtersdeclare @intfilter intdeclare @bigintfilter bigintexec sp_trace_setstatus @TraceID, 1-- display trace id for future referencesselect TraceID=@TraceIDgoto finisherror: select ErrorCode=@rcfinish: go[/code][/quote]Will do! thanks. I will let you know the outcomeSat, 06 Apr 2013 14:36:56 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxSince we're going nowhere fast here...Finish this script (the file name) and then run this trace for a couple of days. It will pick up all backups, all restores and all changes of recovery model. After a couple days, open up the trace output in profiler, see what else is taking full backups, if there are any log backups that explicitly truncate the log and if there are any changes in recovery model.[code="sql"]/****************************************************//* Created by: SQL Server 2008 R2 Profiler *//* Date: 2013/04/06 17:18:38 *//****************************************************/-- Create a Queuedeclare @rc intdeclare @TraceID intdeclare @maxfilesize bigintset @maxfilesize = 100;exec @rc = sp_trace_create @TraceID output, 0, N'InsertFileNameHere', @maxfilesize, NULL if (@rc != 0) goto error-- Client side File and Table cannot be scripted-- Set the eventsdeclare @on bitset @on = 1exec sp_trace_setevent @TraceID, 115, 1, @onexec sp_trace_setevent @TraceID, 115, 6, @onexec sp_trace_setevent @TraceID, 115, 10, @onexec sp_trace_setevent @TraceID, 115, 14, @onexec sp_trace_setevent @TraceID, 115, 11, @onexec sp_trace_setevent @TraceID, 115, 12, @onexec sp_trace_setevent @TraceID, 128, 1, @onexec sp_trace_setevent @TraceID, 128, 6, @onexec sp_trace_setevent @TraceID, 128, 10, @onexec sp_trace_setevent @TraceID, 128, 14, @onexec sp_trace_setevent @TraceID, 128, 11, @onexec sp_trace_setevent @TraceID, 128, 12, @on-- Set the Filtersdeclare @intfilter intdeclare @bigintfilter bigintexec sp_trace_setstatus @TraceID, 1-- display trace id for future referencesselect TraceID=@TraceIDgoto finisherror: select ErrorCode=@rcfinish: go[/code]Sat, 06 Apr 2013 09:21:30 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxThat however is not a native backup error. You have a 3rd party product also backing the DB up? What is it?Sat, 06 Apr 2013 09:08:23 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspx[quote][b]GilaMonster (4/5/2013)[/b][hr][quote][b]mqbk (4/5/2013)[/b][hr][quote][b]GilaMonster (4/5/2013)[/b][hr]Check the SQL error log. Are you seeing recovery model changes? Do you have any other scheduled jobs that do anything to the log (including truncate it)? Do you have any 3rd party backup tools running against this database?What version, since it's clear now that it's not a SQL 2000 database?[/quote]I viewed the error log and this is what I saw:2013-04-05 09:39:45.75 Backup BACKUP failed to complete the command BACKUP DATABASE MSNDirectPay. Check the backup application log for detailed messages.[/quote]So your full backups are failing? If that's the case, and this wasn't an isolated failure, there may well not be a current database backup. What backup tool are you using for backups there? That's not a native backup failure message.[/quote]I have actually run several successful full backups since that message. I have checked it by restoring it onto out development environment. I am using the native backup clientSat, 06 Apr 2013 08:43:15 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspx[quote][b]mqbk (4/5/2013)[/b][hr][quote][b]GilaMonster (4/5/2013)[/b][hr]Check the SQL error log. Are you seeing recovery model changes? Do you have any other scheduled jobs that do anything to the log (including truncate it)? Do you have any 3rd party backup tools running against this database?What version, since it's clear now that it's not a SQL 2000 database?[/quote]I viewed the error log and this is what I saw:2013-04-05 09:39:45.75 Backup BACKUP failed to complete the command BACKUP DATABASE MSNDirectPay. Check the backup application log for detailed messages.[/quote]So your full backups are failing? If that's the case, and this wasn't an isolated failure, there may well not be a current database backup. What backup tool are you using for backups there? That's not a native backup failure message.Fri, 05 Apr 2013 17:45:56 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxif I try to manually run it, it tells me that it doesn't have access to the fileFri, 05 Apr 2013 17:18:42 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxRun a trace in between the full backup and log backups. Capture things and look for any backup or truncate messages.Something must be breaking the chain if this is not working.If you manually run a log backup when this happens, what is the result?Fri, 05 Apr 2013 16:26:30 GMTSteve Jones - SSC EditorRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspx[quote][b]GilaMonster (4/5/2013)[/b][hr]Check the SQL error log. Are you seeing recovery model changes? Do you have any other scheduled jobs that do anything to the log (including truncate it)? Do you have any 3rd party backup tools running against this database?What version, since it's clear now that it's not a SQL 2000 database?[/quote]I viewed the error log and this is what I saw:2013-04-05 09:39:45.75 Backup BACKUP failed to complete the command BACKUP DATABASE MSNDirectPay. Check the backup application log for detailed messages.There aren't any other jobs running that have anything to do with the log files. This is on SQL Server 2005.Fri, 05 Apr 2013 16:15:12 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxCheck the SQL error log. Are you seeing recovery model changes? Do you have any other scheduled jobs that do anything to the log (including truncate it)? Do you have any 3rd party backup tools running against this database?What version, since it's clear now that it's not a SQL 2000 database?Fri, 05 Apr 2013 15:55:52 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxIt's Full and as near as I can tell, always has been.Fri, 05 Apr 2013 15:21:05 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxFor the database in question, what is the current recovery model?Fri, 05 Apr 2013 14:58:19 GMTLynn PettisRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxThat's what every forum I've seen has said. As near as I can tell, It hasn't been changed from simple back to full, but just to make sure I ran a full back up and it is still giving me that error. I looked to see if anything is truncating the log file, but I was not able to find anything similar to that. Here is the script:declare @sql varchar(2000), @dbname varchar(255), @servername varchar(255), @datestr varchar(50)-- you must add entry for this variableif (select serverproperty('instancename')) is nullbegin set @servername = (select @@SERVERNAME)endif (select serverproperty('instancename')) is not nullbegin set @servername = (select convert(varchar(200),serverproperty('instancename')))enddeclare @date datetimeset @date = GETDATE()set @datestr = CONVERT(char(4),datepart(YEAR,@date)) + right(N'0' + convert(nvarchar(2), month(@date)), 2) + right(N'0' + datename(d, @date), 2) + right(N'0' + datename(HOUR, @date), 2) + '0000' declare c_1 cursor for select name from master.sys.databases where state_desc = 'online' and recovery_model_desc = 'full' order by name open c_1 fetch next from c_1 into @dbnamewhile @@FETCH_STATUS &lt;&gt; -1beginset @sql = 'backup log ['+@dbname+'] to disk = ''\\svratlbackup01\sqlbackups011\'+@servername+'\'+@dbname+'_'+@datestr+'.trn'' with init'exec(@sql)fetch next from c_1 into @dbnameendclose c_1deallocate c_1goFri, 05 Apr 2013 14:54:52 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxThe number of log files is irrelevant.What, exactly, does the log backup job do? Post the sql script from it if you can.There are two common causes of this error: Running a log backup after a switch to simple and back to full without taking another full backupExplicitly truncating the log and than not taking a full backup.The first will leave evidence in the SQL error log, the second won't iirc.Fri, 05 Apr 2013 12:58:58 GMTGilaMonsterRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxthe full backup runs in full model. Also I don't see anything truncating the log file. this is really frustrating because all of the other databases are running smoothly just this one is not working, and from the error log I posted it appears to be an issue with the second log file. The database has two log files.Fri, 05 Apr 2013 10:31:50 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxWhen you say check the event logs, do you mean the windows event logs?Fri, 05 Apr 2013 10:00:46 GMTmqbkRE: Backup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxMost likely someone's switched the DB to simple recovery and back to full since the last full backup. As such, there's no current database backup to base the transaction log backups on, so they will fail. Someone could also have explicitly truncated the log (backup log with truncate only)Check for anything switching the DB to simple/full (it'll be in the error log), check for explicit log truncations (they're not in the error log, so you'll need a profiler trace). check what exactly the backup jobs do. I've before now seen a full backup job that ran a backup then switched the recovery model straight afterwards.Fri, 05 Apr 2013 09:30:26 GMTGilaMonsterBackup Log cannot be performed because there is no current database backuphttp://www.sqlservercentral.com/Forums/Topic1439262-24-1.aspxI have a job that runs every two hours starting at 7 AM and ending at 5 to back up my transaction logs. The issues is for some reason it fails, but when you look at the even log it looks like every "user database" log file was created successfully, but it has a huge red x next to it. I then selected Log to table from the advanced options of the job just to see if I could find more information, and there it was my log file couldn't be backed up because there is no current database. I checked to see if the database was in simple mode, and it isn't. It's in full mode. I re-ran a full back up of the database it when off with out a hitch, but when I started the transaction log job again, it fails at the same spot. I did notice that the database has two log files attached to it. I am not sure what I am missing. Can anyone help?BACKUP LOG successfully processed 40 pages in 0.031 seconds (10.372 MB/sec). [SQLSTATE 01000]Processed 0 pages for database &lt;Database name&gt;, file &lt;Database_Log 1&gt;on file 1. [SQLSTATE 01000]Processed 76 pages for database &lt;Database name&gt;, file &lt;Database_log 2&gt; on file 1. [SQLSTATE 01000]BACKUP LOG successfully processed 76 pages in 0.055 seconds (11.245 MB/sec). [SQLSTATE 01000]Msg 4214, Sev 16, State 1, Line 1 : BACKUP LOG cannot be performed because there is no current database backup. [SQLSTATE 42000]Msg 3013, Sev 16, State 1, Line 1 : BACKUP LOG is terminating abnormally. [SQLSTATE 42000]Fri, 05 Apr 2013 08:48:09 GMTmqbk