Skip to main content
Solved

Veeam SQL Plugin - Database Restore Error

  • January 20, 2026
  • 5 comments
  • 43 views
L
  • lgh
  • Comes here often

Hi VC,

I’m wondering if anyone can help, I’m hopeful someone's had this before.

 

We have two SQL servers, one which I am backing up with the Veeam SQL plugin at database level and then restoring to the other using the same plugin through the restore function.

When attempting to restore I’m getting the following error:
 

 

Any ideas what I can check?

Many thanks,

LGH

Best answer by coolsport00

Hi ​@lgh - aside from what Chris and Marcel suggest, you can also take a look at Plugin logs for hopefully more detailed info on what the issue could be:

On the SQL Server
%PROGRAMDATA%\Veeam\Backup\MSSQLPluginLogs

On the Backup Server
%PROGRAMDATA%\Veeam\Backup\Plugin

Maybe something in those will help. I wasn’t able to find anything on the Internet about your specific Plugin error. At the very least you can get ahold of Veeam Support as well. 

    5 comments

    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • January 20, 2026

    It seems like the backup device or location is busy/locked somehow.  Is there AV or something else using it while you are trying to restore?

    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
      Marcel.K
      Forum|alt.badge.img+11
      • Marcel.K
      • Veeam Legend
      • January 20, 2026

      Hi, did you created empty database before restore?

      do you see restore points? - this is as pre-requisite - xml file has to have configured proper repository and hostname has to be changed to original.

      Marcel Kačmár | VCSP Partner 2022 | VMCE 2024 | VMCA 2024 | Veeam Legend 2025 |
        coolsport00
        Forum|alt.badge.img+21
        • coolsport00
        • Veeam Legend
        • Answer
        • January 20, 2026

        Hi ​@lgh - aside from what Chris and Marcel suggest, you can also take a look at Plugin logs for hopefully more detailed info on what the issue could be:

        On the SQL Server
        %PROGRAMDATA%\Veeam\Backup\MSSQLPluginLogs

        On the Backup Server
        %PROGRAMDATA%\Veeam\Backup\Plugin

        Maybe something in those will help. I wasn’t able to find anything on the Internet about your specific Plugin error. At the very least you can get ahold of Veeam Support as well. 

        Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
          matheusgiovanini
          Forum|alt.badge.img+8

          OS error 995 is a generic Windows I/O error and usually means the backup device or restore process was interrupted.
          I’d suggest checking AV/EDR interference, confirming the repository isn’t busy, and verifying that the target database doesn’t already exist (or use overwrite).
          Also make sure restore points are visible and the XML is pointing to the correct repository and original hostname.

          Matheus Giuliano Giovanini | Senior Backup Analyst | Veeam Legend | Blog: techdirectarchive.com
            L
            • lgh
            • Author
            • Comes here often
            • January 21, 2026

            Hi ​@lgh - aside from what Chris and Marcel suggest, you can also take a look at Plugin logs for hopefully more detailed info on what the issue could be:

            On the SQL Server
            %PROGRAMDATA%\Veeam\Backup\MSSQLPluginLogs

            On the Backup Server
            %PROGRAMDATA%\Veeam\Backup\Plugin

            Maybe something in those will help. I wasn’t able to find anything on the Internet about your specific Plugin error. At the very least you can get ahold of Veeam Support as well. 

            Thank you all for your responses.

             

            It’s fair to say you can underestimate logs sometimes, but this time I found the following entry:

            [20.01.2026 13:47:24.711] < 26944>          | ERR |File does not exist. File: [e9b9866c-8dfd-43be-b2b5-e546f4f9b1a2.vab].
            [20.01.2026 13:47:24.711] < 26944>          | >>  |Failed to open storage for read access. Storage: [e9b9866c-8dfd-43be-b2b5-e546f4f9b1a2.vab].
            [20.01.2026 13:47:24.711] < 26944>          | >>  |--tr:Failed to open storage [HostFS://E:\Backup\QLSQL-01 Microsoft SQL backup (VEEAM-DATA)\e9b9866c-8dfd-43be-b2b5-e546f4f9b1a2.vab] ticket of external storage [{00000000-0000-0000-0000-000000000000}]
            [20.01.2026 13:47:24.711] < 26944>          | >>  |--tr:Failed to open storage tickets
            [20.01.2026 13:47:24.711] < 26944>          | >>  |--tr:Cannot apply patches stored in folder [HostFS://E:\Backup\QLSQL-01 Microsoft SQL backup (VEEAM-DATA)\e9b9866c-8dfd-43be-b2b5-e546f4f9b1a2.vab[/]].
            [20.01.2026 13:47:24.711] < 26944>          | >>  |--tr:Failed to build restore point.
            [20.01.2026 13:47:24.711] < 26944>          | >>  |--tr:Failed to replicate content of the backup item [eda900ae-9d6c-4101-8322-934c4c9dea23]. Target file: [].

             

            Turns out that the backup files produced as a result of the plugin doing it’s thing were actually deleted from the main repository (manually). As a result they were not restorable of course, however those deleted entries from previous backups still appear in the restore GUI - something which I’ve fed back to Veeam Support.

             

            Thanks again.

            Terms & ConditionsAccessibility statement