Hi all,
I'm really hoping someone can shed some light on my issue as struggling with online searches. I'm fairly new to VMWare and ESXi so this is a bit of a struggle for me. I've taken on IT support for a friends company who currently use Veeam to backup 2 VM's hosted on ESXi. Both of the backups fail with the below error message:
Processing SERVERNNAME Error: Access is denied. Failed to process [isFileExists].
So I tried installing Altaro instead, however, now one VM backs up fine but the other one throws up this error:
Failed to read from the disk. Error Code: 13 – You do not have access rights to this file (ALTERR_VMWAREBACKUPSTREAM_010)
Its strange how its just the one VM failing to backup with the access denied error on Altaro but both on Veeam.
Any help at all is greatly appreciated. Many thanks.
Stuart.
Hi vXav,
Thanks for the response. I am using the root user which I use to login to the ESXi interface.
I've also checked to ensure it has all the permissions which it does and tried creating a new roll without any luck.
It is strange that one VMs works but not the other.
A few questions out of the blue:
Hi there,
Thinking about it, the one VM backups because the backup software (Altaro) is actually running on that VM. Veeam however is on the other VM and that doesn't back itself up which is really weird .
Try using UPN connotation (user@xx.yy) instead of xx\user where it applies - Unfortunately this didn't work either.
Sorry, I don't follow? The username wouldn't be accepted and no, wouldn't apply here as it doesn't use that format within the backup applications. Besides the root of ESXi and windows credentials; I'm unsure why it's not granting the permissions.
Oops sorry my mistake, there was supposed to be a link :s
https://www.reddit.com/r/Veeam/comments/6r6i4f/error_access_is_denied_failed_to_process/
Surely due to the fact that 2 different backup applications show the same error then it's more to do with VMWare than the backup applications itself?
I have the EXACT same problem. Only one machine in a VM host is yielding this error. Did you find a solution?