Challenge
When backing up a virtual machine running a Microsoft SQL server with disabled TLS 1.0 using the application-aware processing, a backup job may fail with the error code 0x80004005 [TLS 1.0]. Such an error may occur due to the SQL log truncation failure.
The GuestHelper logs in the C:\ProgramData\Veeam\Backup\VeeamGuestHelper_<dd.mm.yyyy>.log file will contain lines such as:
4/26/2016 4:48:52 AM 4004 INFO Connecting to mssql, connection string: Provider='sqloledb';Data Source='(local)\SQL2012SP1';Integrated Security='SSPI';Persist Security Info=False, timeout: 15 4/26/2016 4:49:08 AM 4004 WARN Code = 0x80004005 4/26/2016 4:49:08 AM 4004 WARN Code meaning = Unspecified error 4/26/2016 4:49:08 AM 4004 WARN Source = Microsoft OLE DB Provider for SQL Server 4/26/2016 4:49:08 AM 4004 WARN Description = [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error. 4/26/2016 4:49:08 AM 4004 WARN COM error: Code: 0x80004005
Cause
The SQLOLEDB Provider does not use TLS 1.2. For more information, see the Microsoft blog post.
Solution
As a workaround, you can use the Native SQL Client Provider by adding the following value to the registry key on the GUEST OS VM:
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Value: UseSqlNativeClientProvider
Type: DWORD
Data: 1
No server restart is required.