Guest Interaction Failing after Veeam 13 Upgrade

[ve_leegregory]

We are having the same issue.

We upgraded to 13 last Tuesday. We had a few issues after the upgrade but t ran fine for the rest of the week, This weekend some of the backups with Application Aware processing enabled are failing.

Support are leaning towards a Firewall issue so I have disabled the firewall on the backup servers, Proxy servers and the Guest server but it still fails. If we disable AAP the backup runs fine.

I have logged a support call with Veeam and will update if we find out what the issue is.

[david.domask]

Hi Lee, welcome to the forums.

Can you please share your case number? It will help us to understand if there is an overarching issue.

As noted previously, not every issue has the same root cause, and while we have seen a slight uptick as seen in this topic on Guest Processing failures, not every case has the same root cause, so important to continue with Support.

[kaffeine]

I was able to resolve my application aware processing errors after update to VBR 13 with Windows Hyper-V Standalone by doing the following:

Navigate to Inventory, Microsoft Hyper-V, Standalone Hosts, Hostname.
Right click the Host, hit properties, click next until "Review".
In my case the "Guest Interaction Proxy" was marked as "will be installed".
After hitting Apply, the Guest Interaction Proxy was installed and application aware processing was working just fine again.

Had the same issue - after upgrading to V13 - while creating backup jobs for new VMs (on W2022 Hosts) and this was the solution. Thank you!

[jc711]

Not sure if its the same but saw this post pop up. We had an issue that was just resolved by a private fix provided by Veeam support which we had the following thread for guest processing failing when performing VIX based guest run time components:

applications-f66/aap-failing-on-most-vm ... 54e28b9c8a

Not sure if it is the same, but may be worth mentioning through your support ticket that hotfix 1210713 exists and they can validate if the hot fix applies to the issue being experienced.

[gonzaord]

Had the same issue - after upgrading to V13 - while creating backup jobs for new VMs (on W2022 Hosts) and this was the solution. Thank you!

Hi,

Tried this but finally had to:
- Uninstall Al VEEAM componts on HYPER-V host.
- Go to properties from VEEAM console and install everything following your same steps.

Once done Guest Interaction Proxies begin to appear but i still had problems. Checked communication in the Firewall. GIP communicate throug port 6173 and had denies so i had to add also de HYPERV HOST to the Firewall Rules.
Now it seems to work even i still have one SQL server that is not working.

Open Case #08031397

Still struggling a bit. Will se toninght how backup work.
Hope this helps.

[david.domask]

Hi gonzaord, welcome to the forums.

Thanks for sharing your case number and the solutions that assisted so far. Please continue with Veeam Support on the remaining issue, I see there's a pending suggestion regarding Deployment Kits from Veeam Support.