Symptoms
When you back up a virtual machine (VM) with non-component based backup, you notice that the SQL Writer Service does not skip backing up Always On basic availability group databases on secondary. Additionally, you may receive the error log and SQL Writer Service trace that resemble the following:
Error log
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE myDatabase. Check the backup application log for detailed messages.
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
Error: 18210, Severity: 16, State: 1.
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{DeviceId}1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
Error: 18210, Severity: 16, State: 1.
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{DeviceId}2'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
Error: 18210, Severity: 16, State: 1.
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{DeviceId}3'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQL Writer Service log
FilePath: ** SQLWRITER TRACING STARTED - ProcessId: #, ContextId: #FilePath: ** N.B. NOT INITIALIZED BY THE CONSTRUCTORFilePath: ** Current time: #FilePath: ** Command-line: "CommandLine"FilePath: ** Product version: ProductVersionFilePath: DoesInstanceSupportRANUUserInstances: Instance MSSQL13.MSSQLSERVER Edition: Standard Edition
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
The issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 16 for SQL Server 2017
Cumulative Update 7 for SQL Server 2016 Service Pack 2
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Latest cumulative update for SQL Server 2017
Latest cumulative update for SQL Server 2016
References
Learn about the terminology that Microsoft uses to describe software updates.
