FIX: Error occurs when you back up a virtual machine with non-component based backup in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

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 CONSTRUCTOR
FilePath: **  Current time: #
FilePath: **  Command-line: "CommandLine"
FilePath: **  Product version: ProductVersion
FilePath: 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:
About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all thehotfixes and all the security fixes that were included with the previouscumulative update. Check out the latest cumulative updates for SQL Server:

References


Learn about the terminology thatMicrosoft uses to describe software updates.