FIX: Timeout when you back up a large database to URL in SQL Server 2014 or 2016

Applies to: SQL Server 2014 EnterpriseSQL Server 2016 Enterprise

Symptoms


Consider that you back up your database to URL (the Azure blob) by using the SQL Server BACKUP DATABASE command or Managed Backup. If the backup is very large, some requests between the SQL Server and the Azure Blob storage service may time out, and the backup operation may fail. Additionally, you receive an 1810 error message that resembles the following in the SQL Server error log file:

date time Backup      Error: 18210, Severity: 16, State: 1.
date time Backup      BackupIoRequest::ReportIoError: write failure on backup device 'https://xxxx.blob.core.windows.net/xxx/full/xxxx_FULL_20170211_230001.bak'. Operating system error Backup to URL received an exception from the remote endpoint. Exception Message: The client could not finish the operation within specified timeout..
date time Backup      Error: 3041, Severity: 16, State: 1.
date time Backup      BACKUP failed to complete the command BACKUP DATABASE mydbname. Check the backup application log for detailed messages.

Cause


This issue occurs because the timeout value of the I/O operation to the Azure blob is not long enough. This fix changes the timeout value to a longer flexible value to avoid the timeout frequency of the I/O operation.

Resolution


This issue is fixed in the following cumulative updates for SQL Server:

 Cumulative Update 8 for SQL Server 2016 RTM

 Cumulative Update 5 for SQL Server 2016 SP1

 Cumulative Update 6 for SQL Server 2014 Service Pack 2

 Cumulative update 10 for SQL Server 2012 SP3

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology Microsoft uses to describe software updates.