System failed to flush data to the transaction log

Question

System failed to flush data to the transaction log

info-849042

Ten Centuries

Points: 1108
More actions
August 14, 2010 at 2:43 pm

#224867

Hi,
I am currently taking transaction log backups on my server. However, I am getting warnings:
The system failed to flush data to the transaction log. Corruption may occur.
How could I fix this? I am using backupassist to do transaction log backups (and a full backup of every database beforehand).
Thanks

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

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

What's backupassist?

That error indicates there was some problem writing to the tran log. Investigate the windows event log, any and all RAID/SAN logs and do a CheckDB on the affected databases as soon as possible.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

info-849042 Ten Centuries Points: 1108 More actions · Answer 2

BackupAssist is a backup software I am using. I thought that maybe a cause for the problem?

I will check the event logs ASAP. I am backing up to USB drive so don't have any RAID arrays to check for errors.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

It's not the backup drive that you need to look at. The error's not saying it can't write to the backup file. It's saying that it cannot write to the transaction log, the ldf. Whatever drive that is on is the one you need to look at.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Rick.Cornell.SME SSCrazy Eights Points: 8597 More actions · Answer 4

I had the same issue using Netbackup vs. the Enterprise edition awhile back. After we did a backup it would not truncate the log? So we had to due manually. That became too much as the Enviroment grew! Then we made the decision to do the SQL backup through SSMS, then had the network admins to backup my .BAK and .TRN files.