The error message may display as similar message:
Msg 61700, Sev 19, State 1: Unexpected termination on thread: 0, Return code: x0, VDI Return code: x80770004. BACKUP DATABASE is terminating abnormally. A nonrecoverable I/O error occurred on file VDI_C7BFFD0C-A35F-41C2-A5A2-8B12CF288FAD_0: 995(The I/O operation has been aborted because of either a thread exit or an application request.). The transaction log for database model is full.
The transaction log for database databasename is full.
Transaction log is full
WORKAROUND:
To recover from a situation where the transaction logs grow to an unacceptable limit, you must reduce the size of the transaction logs. To do this, you must truncate the inactive transactions in your transaction log and shrink the transaction log file.
When the transaction logs grow to an unacceptable limit, you must immediately back up your transaction log file. While the backup of your transaction log files is created, SQL Server automatically truncates the inactive part of the transaction log. After you manually truncate the transaction log files, you must create a full database backup before you create a transaction log backup.
See Books Online, Microsoft Knowledge Baseor Microsoft Help & Support for information regarding DBCC SHRINKFILE.
See: http://support.microsoft.com/kb/873235
For additional information about the issues that may occur when you truncate the transaction log files, view the article in the Microsoft Knowledge Base: http://support.microsoft.com/kb/62866/
