Wrong registry key kills B&R Application aware processing (#08074972)

[ibschreiber]

Hi everyone,
After upgrading to V13, we ran into issues with Application aware processing through VBR.

No Hyper-V production Snapshots could be generated on multiple machines spread over multiple customers (we're VCSP).

After a long search and trying everything we knew of this issue with previous versions, the solution came in form of a redid post from mazvazzeg (thank you!)

The issue were not missing open firewall ports, user rights, failed vss providers or anything like this.

Veeam changed the service entry for the Hyper V Volumeshadow requestor which prevented it from running at all:

The failed entry for the registry data under

Code: Select all

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmicvss

contained in the ImagePath key

Code: Select all

 %systemroot%\system32\svchost.exe -k VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard -p

which prevented the service from starting at all.
after changing it back to the value

Code: Select all

%SystemRoot%\System32\svchost.exe -k VeeamHvVssGroup -p

the service is starting again and everything is back to normal.

I'm waiting for Veeam to clarify, if this is a viable solution (at least it's a working one for me) and if there is a different way to fix this.

I'll keep you posted
Michael

[ibschreiber]

This is the original post: https://www.reddit.com/r/Veeam/comments ... ing/?tl=de

[david.domask]

Hi Michael,

Thank you for sharing the solution you located, and sorry to hear about the troubles.

Please do continue with Support, I'm not able to quickly find any details on VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard or how it would have been set like that, so while it's good backups are running, as you noted let's see the results of the investigation.

I've notated the case for Support with some additional details, so let's see how the investigation goes.

[Samuraj]

Hi,
I also encountered this problem on a newly installed SQL server on Hyper-V. Older SQL servers are backed up fine.

Code: Select all

Warning : Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) ... Production checkpoints cannot be created for ...

Unfortunately, I couldn't find this post, so I spent 2 days trying to figure it out. I found that the Hyper-V Volume Shadow Copy Requestor service (vmicvss) is not running and cannot be started.

Finally I found the key mentioned here in the registry, which had a different value than on the other servers. After editing the service started and everything works.

So I was now looking for what the VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard value means and came across this post.