Per risolvere l’errore a causa della mancanza di supporto TLS 1.2 di SQL Server.
04.12.2020 04:34:05 :: Unable to truncate Microsoft SQL Server transaction logs. Details: Failed to call RPC function ‘Vss.TruncateSqlLogs’: Error code: 0x80004005. Failed to invoke func [TruncateSqlLogs]: Unspecified error. Failed to process ‘TruncateSQLLog’ command. Failed to truncate SQL server transaction logs for instances: . See guest helper log. .
Cause
Solution
The direct solution to this situation is to review available updates for the SQL Server that is having this issue and ensure that TLS 1.2 is supported by the Microsoft OLE DB provider for SQL Server.
Please review: https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server
As a workaround, it is possible to force Veeam to request that the ‘Native SQL Client Provider’ be used instead of SQLOLEDB. This is done by adding a registry value to the Guest OS of the machine being protected by Veeam.
Please review the scenarios below and use the location and value specified:
- For a VM being protected by Veeam Backup & Replication:
- Location: HKLMSOFTWAREVeeamVeeam Backup and Replication
- Value: UseSqlNativeClientProvider
- Type: DWORD
-
Data: 1
- For machines being protected (managed or standalone) by Veeam Agent for Microsoft Windows:
- Location: HKLMSOFTWAREVeeamVeeam Endpoint Backup
- Value: UseSqlNativeClientProvider
- Type: DWORD
-
Data: 1
- For SQL Failover Clusters protected by Veeam Agent for Microsoft Windows via a job in Veeam Backup & Replication with the option Backup logs periodically an additional value must be specified (the value in HKLMSOFTWAREVeeamVeeam Endpoint Backup also still remains the place).
- Location: HKLMSOFTWAREVeeamVeeam Backup and Replication
- Value: UseSqlNativeClientProvider
- Type: DWORD
- Data: 1
No server restart is required, registry key will be checked on next job run.