Reading Time: 2 minutes

The new Veeam Backup & Replication 9.5 Update 3a patch may introduce some warnings backing up Microsoft SQL Server VMs after installing the update.

It does not happen in all cases, and seems more limited for SQL Express instances.

But Veeam has described the issues in KB2689 ( with also the required fix!

After upgrading Veeam Backup & Replication 9.5 to Update 3a, you may notice  warning or failures on the following operations:

  • Back up of SQL Server transaction logs;
  • Truncation of SQL Server transaction logs;
  • Collection of SQL instances metadata for Veeam Explorer for SQL (VESQL)

While the error message varies depending on the actual operation, there is a common error thrown in the job sessions:

"Logon failure: the user has not been granted the requested logon type at this computer. Code: 1385"

The first issue is due to a change in the required rights of account used for Application-Aware Processing.

Update 3a requires that this account has the following user right assigned:

  • Logon as a batch job granted.
  • Deny logon as a batch job not set.

The second issue is caused by changes in the permission error handling the logic of Veeam Backup & Replication.

There are different ways to fix this problem (is existing) but the faster is to apply a hotfix which changes the application processing logic for SQL Servers.

To install the hotfix:

  1. Stop Veeam jobs and Veeam services
  2. Make a backup copy of the following files, from the backup server and all guest interaction proxies:
    • C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Core.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.VssProvider.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\sql\VeeamLogShipper_X64.exe
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\sql\VeeamLogShipper_X86.exe
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\sql\VeeamLogShipper_X64.exe
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\sql\VeeamLogShipper_X86.exe
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2008R2_X64.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X64.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X86.dll
    • C:\Program Files\Veeam\Backup and Replication\Backup\VSS\VeeamGuestHelpers\VeeamVssSupportXP_X86.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupport2008R2_X64.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X64.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupport2003_X86.dll
    • C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers\VeeamVssSupportXP_X86.dll
  3. Replace the files listed in the previous step with those found in the hotfix package
  4. Start Veeam services on server

But the best (and long-term solution) is to adjust permissions and rights of the account specified with for use with Application-Aware Processing within the Veeam Backup & Replication jobs. More information can be found in the updated system requirements.