Operational Defect Database
BugZero found this defect 3319 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2027
Job reports warning "Failed to truncate transaction logs for SQL instances: Possible reasons: lack of permissions, or transaction log corruption."
Last update date:
1/12/2023
Affected products:
Veeam Backup & Replication
Veeam Agent for Microsoft Windows
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
Backup Job with Application-Aware Processing enabled and configured to "process transaction logs" displays the warning:
Solution
Confirm that the account used by Veeam has required permissions The account used by Veeam to perform truncation must have the required SQL permissions as outlined here. For Virtual Machines (vSphere/Hyper-v), the account is specified on the Guest Processing tab of the Backup Job. For machines backed up using Veeam Agent for Microsoft Windows, the account used for SQL Truncation is the account used to add the machine to the Protection Group. If SQL Truncation cannot be performed with the specified account, the software will failover and attempt to use the NT AUTHORITY\SYSTEM account.
Advanced Troubleshooting
Review log files to identify the issue To investigate why SQL log truncation has failed, the Veeam logs will need to be reviewed to determine which part of the truncation procedure failed. For Veeam Backup & Replication, the log file containing information about the truncation procedure will be found on the SQL server, and is named: C:\ProgramData\Veeam\Backup\VeeamGuestHelper_ddmmyyyy.log Within the VeeamGuestHelper log file, beneath the line "Transaction log truncation statistics," you will see information about which account was used, which SQL instances were processed, and a list of each database that was interacted with.
