https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzQ2IiwiaGFzaCI6ImIxYmJkNmIyLWM1OTktNGRjNy05NzYyLTM1MTRkMTgzZDM3ZCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Log truncation issue on Microsoft SQL server

Challenge

Logs are not truncated on Microsoft SQL server after a successful backup.

The following error can be found in the Windows Application log or in VeeamGuestHelper.log file (in earlier versions this log file is called VeeamVSSSupport.log) located in C:\ProgramData\Veeam\Backup on the guest:

 
The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "Database name" under the current security context.' 
or

The server principal "domain\username" is not able to access the database "Database name" under the current security context.' 
 

Cause

Depending on Veeam B&R version there may be different causes:

In Veeam B&R prior to v8:
By default, LOCAL SYSTEM account does not have log truncation rights on SQL 2012.


In Veeam B&R v8:
Starting with version 8, Veeam uses the account specified on “Guest Processing” tab in the job settings for log truncation. This user account may not have required user permissions for performing database backup or log truncation.
 

Solution


Depending on Veeam B&R you need to apply the following settings either for NT AUTHORITY\SYSTEM (pre-v8) or for the user specified in the backup job (v8):

User-added image

 
KB ID:
1746
Product:
Veeam Backup & Replication
Version:
6.5, 7.x, 8.x, 9.x
Published:
2013-04-04
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later