T-Log Backups fail from 7am to Noon

This is a weird one. I have my server backing up the tlogs every 15 minutes 24 hours a day. Every day between 7 am and 12 noon they fail. I can't figure out why. Nothing that I know about happens between 6:45 and 7am that would cause an error. At 7am I get error 8309 in the App Event log.

BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.

I don't get this at any other point in the day. After that I get a messages that the backup plan fails until noon. At noon the full backup runs, and then the TLog backups start running again.

In the SQL log I get this..

Executing the query "BACKUP LOG [libData] TO DISK = N'E:\\sqlBackups\\tlogBackups\\libData\\libData_backup_200606151045.trn' WITH NOFORMAT, NOINIT, NAME = N'libData_backup_20060615104501', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "BACKUP LOG cannot be performed because there is no current database backup.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

I am really at a loss as to what could cause this. Any suggestions would be helpfull

Answer this question

T-Log Backups fail from 7am to Noon

_ilya_
Hi there,

How do we stop this error message from occurring Can we prevent it

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 8309
Description:
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

Thanks,

Fordy.
prenders

Your error message pretty much says it all:

"BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log."

Between 6:45 and 7AM, you have something or someone issuing either a backup log with truncate only or backup log with no log. Once this happens, your tran log backups will start to fail. Since you have a full backup that kicks off at noon, the tran log backups are going to work fine after that point.
jenn hweehuangdong
The T-Log backups run ever 15 minutes all day long. From 7am to noon there is an error and they abort. The rest of the day they run fine.
LeXXik
Thanks for your answer Michael.
mklynx
Sorry about the long delay. I used the maintance plan wizard to set up this job. Why would it use a deprecated command. How do I change that command if it was created by the wizard

Thanks

Rob
avi_india
How frequently do your transaction log backups run When is the last tran log backup that runs sucessfully
syiown8
Thank you. You where absolutly correct. Someone had slipped a job in there that was issuing this command. I Stopped the job and everything is running smooth.

Thanks again
Rob
ITSMEAGAIN

Well, you stop it from occuring by not issuing the command. You prevent anything from being able to issue that command by ensuring that no one has been added to the db_backupoperator role, db_owner role, or sysadmin role other than an account you can trust to not issue that command.

The message will occur every time someone executes either of those commands.
T-Log Backups fail from 7am to Noon

Answer this question