My company uses Veeam Backup & Replication to make backups of our VMWare-hosted virtual machines. We use Veeam's SQL log backup feature for our MS SQL 2008 R2 server. Our backup repository resides on a Buffalo TeraStation TS-XLBF NAS.
Jul 02, 2017 SQL Server not available. The backup was configured in a earlier version of the agent without a problem. When I now try to click on configure backup, I get a message that the microsoft SQL server hosting the configuration database is not available. That is correct. No SQL server running on any of my pc's or NAS. I had to bring down our Veeam server today to add another network card for our iSCSI connections. Home Storage & Backup Data Backup. Veeam service is not running, won't start. By ninjageek. So I was wondering how do I go about verifying Veeam is using the correct name. I'm not a SQL guy at all.
At some point, we started getting error reports of this kind:
Failed to save transaction log backup file for database [DB name] to repository: Der angegebene Netzwerkname ist nicht mehr verfügbar. Error code: 64 Failed to flush file buffers. File: [path to .vlb file]. Failed to backup file. File: [file description] Failed to save transaction log backup file for database to repository: Der angegebene Netzwerkname ist nicht mehr verfügbar. Error code: 64 Failed to flush file buffers. File: [file name]. Failed to backup file. File: [file description] Transaction logs from some databases were not backed up for the last 38 intervals
The text in German (Der angegebene Netzwerkname ist nicht mehr verfügbar) states, The specified network name is no longer available.
As it turns out, this error occurs every Monday night during the scheduled time for the regular backup jobs. The VM backups themselves are completed successfully, only the SQL log backup is affected.
The error messages are sent every few minutes but stop once we restart the system that's running Veeam. Looking for the cause of the issue, I found an article on the Veeam website describing this exact error message. The article identifies issues with de-duplication on NTFS storage as the root cause. Since the TeraStation is a Linux system using XFS, which doesn't support de-duplication, I don't think this applies in our case.
I also tried accessing the backup repository using the path mentioned in the error message, while the error messages were still being generated. I was able to access the resource successfully, so I guess name resolution is not the issue.
The event logs on the machine running Veeam don't show any error messages. The regular backups of all VMs run without errors.
What could be the cause of the failing SQL server log backup jobs? Is there a way to gather more information about the failure?
waldrumpus
waldrumpuswaldrumpus
Browse other questions tagged backupnetwork-sharesql-server-2008-r2database-backupveeam or ask your own question.
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:ProgramDataVeeamBackup on the guest:
The server principal 'NT AUTHORITYSYSTEM' is not able to access the database 'Database name' under the current security context.'
or
The server principal 'domainusername' is not able to access the database 'Database name' under the current security context.'
or
The server principal 'domainusername' 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.
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 AUTHORITYSYSTEM (pre-v8) or for the user specified in the backup job (v8):