BudaCli (7/4/2012)
Also has more or less similar problem where the issue was not even the backup but the log file.We couldn';t backup the log file and it was increasing at least by 25GB a day.
Couldn't do a log back up but a full DB backup would backup succesful.
When doing a log backup I'd get error below:-
Msg 3203, Level 16, State 1, Line 1
Read on "L:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\FILENAME_log.ldf" failed: 1117(failed to retrieve
text for this error. Reason: 15105) Msg 3013, Level 16, State 1, Line 1BACKUP LOG is terminating abnormally.
This turned out to be something wrong with the disk where the log file was placed.
There are many reasons of large transaction log file size which you can easily find out from here: http://www.recoverdatabase.blogspot.in/2012/04/what-to-do-if-sql-server-log-file.html
Before you try to back up the transaction log for a database in Microsoft SQL Server, you must perform a full database backup. Otherwise, you receive this error message that indicate that the BACKUP LOG statement stops abnormally. You must also perform a full database backup before you try to back up the transaction log for a database in Microsoft SQL Server 2000. However, if you do not perform a full database backup before you back up the transaction log of a database in SQL Server 2000, the BACKUP LOG statement does not stop. For more information about the error, please check this link: http://support.microsoft.com/kb/928317
SQL Database Recovery Expert 🙂