Skip to main content
Solved

SQL Backup Fails After Upgrading Veeam B&R to 13.0.1 – ODBC Driver 17 Error

  • January 29, 2026
  • 4 comments
  • 150 views
A

Hello everyone,

After upgrading Veeam Backup & Replication from version 12.3.2.4165 to 13.0.1.1071, we also upgraded Veeam Plug-In for Microsoft SQL Server using the ISO 13.0.1.1071, which installed Veeam Plug-In version 13.0.1.180.

The upgrade process completed successfully without any visible errors.
However, after the upgrade, SQL Server backups are no longer running successfully.

All SQL backup jobs are now failing with the following error:

Error: [Microsoft][ODBC Driver 17 for SQL Server] Database is invalid or cannot be accessed

Before the upgrade, backups were working correctly with no issues.

Has anyone experienced a similar issue after upgrading to Veeam 13?
Any suggestions on what to check would be greatly appreciated.

Thank you in advance for your help.

Best answer by amyteberi

HI,

actually it was a bug with the Veeam Plug-In for Microsoft SQL Server V13.0.1.180. The plugin failed to authenticate against read-only databases, causing SQL Server to reject the connection. The problem was solved after a fix from veeam support.

 

    4 comments

    Venkata Sai Kumar

    Hi,

    Check The veeam_config.xml file (on the SQL server where the Plug-In is installed) may have invalid or missing entries. 

     

    Refer this artical: https://helpcenter.veeam.com/docs/vbr/userguide/mssql_odbc_driver.html?utm_source=chatgpt.com&ver=13

     

    Chris.Childerhose
    Forum|alt.badge.img+21

    ​@amyteberi  - Just wanted to follow up to see if you found an answer your question. Please mark a best answer if this is resolved including your own if needed.

     
     
     
    Chris Childerhose (Enterprise Architect) - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    A
    • amyteberi
    • Author
    • Not a newbie anymore
    • Answer
    • March 4, 2026

    HI,

    actually it was a bug with the Veeam Plug-In for Microsoft SQL Server V13.0.1.180. The plugin failed to authenticate against read-only databases, causing SQL Server to reject the connection. The problem was solved after a fix from veeam support.

     

      Chris.Childerhose
      Forum|alt.badge.img+21

      Glad to hear you got it resolved.

      Chris Childerhose (Enterprise Architect) - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
      Terms & ConditionsAccessibility statement