Permissions Denied on one backup to repository allowed by others

With ESXI backups, the proxy in use could be the Veeam server, or other Veeam proxies you may have configured. With Hyper-V backups, the proxy is sometimes the Hyper-V host itself.

Does the Hyper-V host the VM is sitting on have access to the NFS repository via these ports?

Thanks. I made sure file/printer sharing was on and can get out to the NAS from the HyperV host. I have full read/wrote permissions from the HV to the NAS, and from the Veeam server to the NAS, yet I’m still getting these errors.

Could you do some isolation testing? Can you set up another repository, perhaps on disk, and back up a small hyper-v VM to it? If it works, that points to the connection to the NAS as the issue. If it doesn’t, then the issue is reading from Hyper-V.

OK backing up locally seems to work. I’m not sure why it won't backup to the NAS when both Veeam and hyperV have R/W access to it. The repository was originally defined to use nfs3 which works well for when backing up VMWare VMs, but I’ve tried both that and smb and get errors, even though I can see the backup flles from the HV server.

Can you check to see if the Hyper-V hosts are added to Veeam configured to use On-Host or Off-Host backup?

Try switching between them to see if there is any difference. Here is how to add an Off-Host backup proxy.

This is a new error when trying to backup over smb:

“...Error: Incorrect function. Agent failed to process method {ReFs.SetFileIntegrity}.”
 

Did you switch the proxy type resulting in the new error?

By the way, if you haven’t already, I recommended creating a case with Veeam support who can dig into the logs and help you out. They may be better equipped to look up the errors you’re getting.

Found a registry Change that fixed the above setfileintegrity error for some, but didn't work.

Thanks I’ll try. Didn’t even occur to me since I’m using the free version.

Yep, they will still provide support, it will just be “Best Effort” from them rather than holding to a strict SLA.

What did you set? I’m a bit surprised that an NFS share threw a ReFS Integrity Check error. Can you confirm:

1. It’s really an NFS repository?
2. Can you post a screenshot of the current error from the UI?
3. What is the config parameter you set for the above?

On which layer did you set the permissions? On the file system of the target repo or on the Veeam repo within VBR?

Found the problem. The separate LAN I use for backups wasn’t configured right on the HV host, and when testing I didn’t notice I was just connecting through the regular LAN. Once I remade the LAN I want to use it could find the IP and get to the repository. I guess Veeam reports “no network” as a permissions error. Thanks.

Glad to hear you were able to solve the issue. When you’re able, please select a comment as “Best Answer”, even if it is your own.