Transaction log backup failing

Question

Transaction log backup failing

dgermundson

Hall of Fame

Points: 3115
More actions
October 14, 2004 at 11:51 am

#86689

Our transaction log backups are failing. The only error I could find said that there was not a complete backup. The problem is there is one. I have the recovery set to full but the tlog backups are still failing. I checked the full backup and it looks fine.
Thanks
Darren

Darren

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

hoo-t SSChampion Points: 12713 More actions · Answer 1

Even though you have a full backup, it seems that the transaction log backups can't associate with it. Perhaps a non-logged operation has occured, or the transaction log has been truncated since that backup was taken. Take another full backup, then see if the transaction log backups won't start working. Ensure that nothing other than a transaction log backup truncates the log, and if a non-logged operation is necessary, immediately take a full backup.

Steve

Don Millhouse SSC Eights! Points: 977 More actions · Answer 2

Perform a full backup again and then the tran log backups should work. If the full backup has an error the tran log backups have no reference point and the full backup must be repeated.

dgermundson Hall of Fame Points: 3115 More actions · Answer 3

I did another full backup last night but it still isn't working. I think maybe our network admin was cleaning up some disk space and deleted some of the tlog backup files. I guess I can try one more time and see if that fixes it. If not, I'm out of ideas. Thanks for the responses.

Darren

apf001 Mr or Mrs. 500 Points: 550 More actions · Answer 4

I think Steve's reply is accurate. I would guess that there is a job running somewhere that has a "truncate log" statement in it. Sometimes people will fill up the transaction log and use truncate to "solve" the problem.

The network guys deleting tlog backup files would not cause this error. By the way, could you post the exact error you're getting?

apf

dgermundson Hall of Fame Points: 3115 More actions · Answer 5

OK, I got it working. The BUILTIN\Administrator account was deleted (by me). The account that the job was running under was using that group for access. What I don't understand is that account had its own login that "should" have the permission to run the job. When I added the BUILTIN back in, it worked. I don't want the BUILTIN account, so what permissions do I need to have on the account to run this? My SQL Server Agent account has SysAdmin rights.

Darren