I have seen may posts on the above topic but not is the resolutions have fixed my problem. The account used is part of the local admin group, is part of the domain administrator group and has log on as a service. When running the backups, most VM’s (VMware) fail with the subject matter. When I run the Test Credential on the same backup group, most pass successfully, but then fail when the backup begins.
At a loss as to where to go to next.
+21Hi
Welcome to the Community. Before I offer some suggestions, first let me ask...do you have a dire need to use ‘Guest Processing’ as it’s called in the Backup Job? In other words, do you have applications (SQL, AD, Oracle, etc) you want to transactionally process using AAIP? If not, there is no need to use this setting. I just offer this 1st suggestion because in my early yrs of using it, I found it very cumbersome to use for the very reason you are experiencing now. Also, if you don’t use Enterprise Manager or have some dire need to use Guest Indexing, again...this section of a Backup Job doesn’t need configured. I know there are some on here & in the Community that configures this, but I mostly know of many who don’t. Just something to think about.
Now...on to what the issue could be. First, you can check logging for the error(s) you’re getting in the following location: C:\ProgramData\Veeam\Back\<backup-job-name>.log. Maybe something will stand out in there. Next, have you read through the Veeam VMW User’s Guide on Guest Processing and the Permissions req’d to run this successfully? Instead of regurgitating the Guide, I’ll just offer a couple links for you to look over to verify if what you have configured is correct.
About Guest Processing and Requirements/Limitations:
https://helpcenter.veeam.com/docs/backup/vsphere/guest_processing.html?ver=120
Permissions required for it:
https://helpcenter.veeam.com/docs/backup/vsphere/required_permissions.html?ver=120#rptcb
About Guest Interaction Proxies, which are used to deploy GIP Agents for the app processing on the clients:
https://helpcenter.veeam.com/docs/backup/vsphere/guest_interaction_proxy.html?ver=120
And lastly, how to configure GP in the Backup Job:
https://helpcenter.veeam.com/docs/backup/vsphere/guest_interaction_proxy.html?ver=120
Read through all of those things and see where you may be missing something. Another couple things which might be causing issues → Windows Firewall (if needing to keep enabled, make sure to create Veeam exclusions) on the client VMs, UAC enabled, and Antivirus (make sure to create Veeam exclusions here too).
I know that’s a lot. I don’t have any explicit “do this” or “do that” suggestions. You always should start from the beginning and work your way up to see what might be going on. You may indeed have everything setup correctly and are still getting these errors. In which case, you simply need to open a case up with Veeam Support.
Best.
+11hi
you must consider one more thing…
when backup job starts guest intercaction proxy is used to logon on the application aware with your credentials.
So please check your servers in backup job are reachable from the proxy.
+2if you are using VIX process method: since the account used for backup is not the Built-in Administrator account (LOCAL\administrator or DOMAIN\administrator), please ensure that UAC is disabled on the Windows servers by modifying the registry and performing a reboot. https://www.veeam.com/kb1788
If you are using the RPC method: Make sure the Guest Interaction Proxy has access to the VMs over the network, and that the necessary firewall ports are allowed between the proxy and the VM. https://www.veeam.com/kb1230
+7You can try disabling UAC using the regedit, but you will need to restart the server.
In the Local Security Policy, you can also try disabling or changing some parameters.
Please check if Windows Defender, antivirus, and Windows WMI are working correctly.
Also, you can check the following KB article:
https://www.veeam.com/kb3225
https://www.veeam.com/kb1230
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
