Goline Logo

News

  • New Partnership Between Goline and EaseUS: Technology and Innovation at Your Service. We are excited to announce our collaboration with EaseUS, a leading company in data management, file recovery, and disk cloning software. This collaboration allows us to provide our users with reliable and cutting-edge tools to manage and protect their devices efficiently. Exploring the Benefits of Our New Partnership with EaseUS This collaboration enhances our capability to deliver top-notch services to our community. With EaseUS, you can optimize storage space, recover lost files, and clone disks easily and securely. Whether you're a home user or an IT professional, you'll...
  • In the supply and logistics sectors, email communication is pivotal. However, organizations face threats like email fraud and phishing. GOLINE SA's clients struggled with configuring email authentication protocols manually. To address this challenge, GOLINE SA partners with PowerDMARC as an MSP Partner, collaborating to streamline implementation and management. PowerDMARC's cloud-based platform automated DMARC, SPF, and DKIM protocols for GOLINE SA's clients. This streamlined the transition to DMARC enforcement policies, bolstering domain protection without compromising email deliverability. The intuitive platform facilitated easy navigation and provided detailed reporting for proactive issue resolution. Strategic Collaboration: GOLINE SA Partners with PowerDMARC GOLINE SA's clients...

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

Cause

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

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:

  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
Subscribe
Notify of
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x