Veeam Backup & Replication: Unable to truncate Microsoft SQL transaction logs | GOLINE
Goline Logo



  • Route RPKI validation April 1st, 2022
    RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems. Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

Veeam Backup & Replication: Unable to truncate Microsoft SQL transaction logs

Paolo Caparrelli Veeam 22 June 2022

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. .


The SQL Server being protected by Veeam is using a SQL OLE DB provider which does not support TLS 1.2


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:

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:

  1. For a VM being protected by Veeam Backup & Replication:
    • Location: HKLMSOFTWAREVeeamVeeam Backup and Replication
    • Value: UseSqlNativeClientProvider
    • Type: DWORD
    • Data: 1
  2. For machines being protected (managed or standalone) by Veeam Agent for Microsoft Windows:
    • Location: HKLMSOFTWAREVeeamVeeam Endpoint Backup
    • Value: UseSqlNativeClientProvider
    • Type: DWORD
    • Data: 1
  3. 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.

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x