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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNDc4IiwiaGFzaCI6ImFjYzIwZjBhLWUxN2UtNDJiZC1iODJjLWE1ZTY1YTU2YzEyZiJ9
1-800-691-1991 | 9am - 8pm ET
EN

SureBackup fails: Access is denied. Failed to create event.

Challenge

A SureBackup job fails, and the following entries can be seen in the JobSB.SureBackup_name.log:

[timestamp] <09> Error    Exception has been thrown by the target of an invocation. (System.Reflection.TargetInvocationException)

[timestamp] <09> Error    NfsService: Failed to mount backup, share id 'xxx', host 'hostname'. (System.Exception)

[timestamp] <09> Error    Access is denied\nFailed to create event [xxx].\nRPC: Failed MountBackup.\n (Veeam.Backup.Common.CAppException)

Cause

This issue occurs when the Proxy server is used as a Backup Repository and Veeam Backup Proxy service is running under the Local System account.

Solution

Make sure the Veeam Backup Proxy service* uses the same credentials that both Veeam NFS and Veeam Backup services run under.

* - in v8 the service is named 
Veeam Data Movers Service

KB ID:
1478
Product:
Veeam Backup & Replication
Version:
6.x,7,8
Published:
2012-01-20
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