Loading...
Loading...
A Microsoft SQL backup fails with the following error: 2023-02-22 21:22:12 avsql Error <40258>: sqlconnectimpl_smo::execute Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: BACKUP detected corruption in the database log . Check the errorlog for more information. A nonrecoverable I/O error occurred on file "(local)_Test_DB-SQL_Backups-1677106800223-3006-SQL:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). BACKUP LOG is terminating abnormally. at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand) --- End of inner exception stack trace ---
The error in the example above (the "Test_DB" database) is due to corruption in the transaction log file (LDF), which is causing the transaction log backups to fail. (Transaction log backups try to back up all transactions generated since the last log backup, including corrupted portions, which cause the backup to fail.) Corruption can occur due to disk space issues on the SQL log drive.
There are three possible solutions to address this issue: Engage Involve the SQL Administrator and request that the specified LDF file be fixed. Once the LDF file is fixed, please run a Full Backup followed by a transaction Log backup. Change the recovery model of the Database from "Full" to "Simple" and then back to Full. This will ignore the corrupted log part from backup allowing the backup to proceed. (The next Avamar backup runs as "Full" because the Recovery Model has changed.) The backups can run the Native SQL Backup with the option " CONTINUE_AFTER_ERROR " to ignore the log part that is corrupted. After this, backups can be resumed using Avamar. (The next Avamar backup run as "Full" because the previous backup was performed "native-level".)
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.