[RESOLVED] Unable to backup any Server 2016 VM's on Hyper-V

[TheRealTy]

Hi,

I am unable to backup any of my server 2016 guests. I keep getting the below errors.

Firewalls are off on host and Guest
No AV on Guest
No other security software
Plenty of disk space on host, guest and backup server
I can ping between all severs
Host an backup server both run server 2016
Guests are fully patched
Checkpoints are working on host
Guests are not cloned, all fresh installed
Guest indexing turned off

Failed to finalize guest processing. Error: Failed to call RPC function 'Vss.WaitForBackupDocsToBeFlushed': The remote procedure call was cancelled. RPC function call failed. Function name: [DoRpc]. Target machine: [10.243.1.4:6190]. 01:00:00

* 10.243.1.4 is the host

I have been directed to MS support by Veeam which feels like a bit of a cop out, cant see how all of my VMs would have the same issue. Unless Veeam cannot backup 2016 at all due to an MS bug?

Lasts support response

"Thanks for the reply. I did check the logs and i see the following :

2/03/2019 6:13:48 PM 13924 Restarting HVVSS service.
2/03/2019 6:13:48 PM 13924 Cannot read retry settings from registry. Using default value 4. Cannot read VmicvssRetryNumber value
2/03/2019 6:13:48 PM 13924 Win32 error:The system cannot find the file specified.
2/03/2019 6:13:48 PM 13924 Code: 2
2/03/2019 6:13:48 PM 13924 Restarting Hyper-V VSS requester
2/03/2019 6:13:48 PM 13924 Stopping Hyper-V VSS Requester

I checked further, it seems to be a known issue with 2016 machines. And work-around is :

Stop the COM + Event System service
Restart the Volume Shadow Copy service
Start the service COM + Event System (Attention do not forget to set the service to "Automatic"!)

This has been applied already. I suggest to contact Microsoft in case you have support agreement for the Hyper-V hosts.
"


Has anyone had similar issues and success in getting them resolved.

Support Case: 03470978

[TheRealTy]

***EDIT**
Veeam Zip also seems to work from the backup server on a 2016 VM

[wishr]

Hi Tyron,

As far as I see from the case info, the conversation is going. Please try out the suggestion made by our engineer and let us know if it worked.

Thanks,
Fedor

[ffwo]

I think, i have the same Problem. Only Server 2016 and 2019 VM's affected. I already opened a Support Case, which was closed, because i only use the Veeam Community Edition.

[ID# 03582223] RPC Problem bei Application Aware Backup

I also posted my Logs into a new Post here - it should appear in the near future.

[ffwo]

Sorry for Crossposting, but i think i have the same Problem:
microsoft-hyper-v-f25/application-aware ... 59647.html

[wishr]

Hi everyone,

I'd like to mention that the initial issue has been resolved by applying a fix. If anybody else experiences the same symptoms - please reach out to our technical support to confirm it and obtain a fix.

Thanks

[illandous]

Is this fix available for the community edition. Calling support asked if I had support and I don't since I'm on the community edition.

[wishr]

Hi Ryan,

Welcome to Veeam Community Forums and thanks for posting.

I understand your frustration, but we do not provide Phone support for Community, Free or NFR licensed products. Email support is provided on a best-effort basis depending on staff availability. Please refer to Veeam Support Policy for more info.

Thanks

[illandous]

Regarding support : That's fine.

Regarding the fix: Is this fix available for the community edition?

[wishr]

The fix is applicable for any B&R edition, yes.

[illandous]

May I have the link to the fix for the community edition?

[Dima P.]

Hello Ryan,

Fixes are distributed by our support team, so please raise a case via customer portal via veeam.com in order to get it. Do not forget to share the case ID and use this thread as a reference for your support request. Hope this helps!

[John Mays]

I fixed my issue by moving the virtual machine storage to another drive, Make sure you do not have drive compression turned on, then I deleted the empty folder that the vm was in, make sure the drive does not have compression turned on, I create a new folder on the drive that originally had the vm running and move the vm again to the newly created folder.

I ran the backup successfully. I spent several days troubleshooting this issue, I hope this helps you.