Hi everyone,
just wanted to share something we hit recently after deploying Veeam B&R v13 in a Hyper-V environment.
The issue
After the upgrade, Application-Aware Processing stopped working.
Symptoms:
- No Hyper-V production checkpoints
- Multiple VMs affected
- Happening across different customers
What we checked
We went through all the usual stuff:
- Firewall → OK
- Permissions → OK
- VSS → OK
- Integration services → OK
Everything looked fine… but still no AAP.
The cause
After a long search, we found a post from mazvazzeg that pointed us in the right direction.
Turns out it’s a wrong registry value for the Hyper-V VSS service (vmicvss).
Path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmicvssWrong value in ImagePath:
%systemroot%\system32\svchost.exe -k VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard -pThis basically prevents the service from starting.
The fix
Change it to:
%SystemRoot%\System32\svchost.exe -k VeeamHvVssGroup -pAfter that:
- Service starts correctly
- AAP works again
- Production checkpoints are created 👍
We’re still waiting for feedback from Veeam on whether this is officially supported or if there’s a better fix.
This is the original post: https://www.reddit.com/r/Veeam/comments/1std7jf/veeam_hyperv_vss_application_aware_processing/?tl=de
Hope this helps someone 👍
Hicham
