Failed to invoke func [GetShadowVolumesListing]

[Robvil]

Hi,

My setup is:
VBR 9.5U2 - using Microsoft VSS software provider for my CSV´s
2 hosts 2012r2 cluster with CSV
Nimble SAN 3.8.0.1 connected with iSCSI mpio
Hyper V integrated services version 6.3.9600.18692 for 2012r2 and 10.0.14393 for 2016 VM. All up to date.

What i see in the Windows VM guest backup logs is:
[30.07.2017 23:02:25] <29> Error Failed to invoke func [GetShadowVolumesListing]: Unspecified error. Failed to process 'GetShadowVolumesListing' command.
[30.07.2017 23:02:25] <29> Error There is no VSS snapshot with ID '{9f0f0584-6529-44e8-832e-8a47b4387714}' or job does not support shadow volumes creation. (System.Runtime.InteropServices.COMException)

Veeam support is 100% sure this is related to Microsoft VSS errors, but looking at VM guests do not show any vss errors at all. Looking at the Hyper V hosts the only thing related to VSS i see is under Hyper-V-shared-VHDX which shows this during backup:

Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy62. Error: The specified request is not a valid operation for the target device..
Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy61. Error: The specified request is not a valid operation for the target device..
Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy62. Error: The specified request is not a valid operation for the target device..
Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy60. Error: The specified request is not a valid operation for the target device..
.....

this is going on for multiple timers during the backup window.

Anyone with any clue where to start looking for changes which could solve this?

Regards
Robert

[foggy]

Hi Robert, I'd appreciate if you share the support case ID.

[Robvil]

ohh, i have no support case id. It is month ago veeam support looked into this, and since then, i have been looking at it on and off.

[foggy]

If you've enabled Veeam support, then you should have an ID. We require case ID to be provided for any technical issue posted on forums, so please look it up in your correspondence. That said, backup of shared VHDX is not supported (MS limitation).

[Robvil]

Well, can´t find my old case ID. but anyhow i´m not using shared VHDX at all, so that´s even more weird.
Mayby I should open a new case....

[foggy]

Yes, please do.

[Robvil]

case ID 02266559

[Robvil]

Removing a Windows 2016 server as a proxy in the backupjob removed the errors in the Veeam backup log, but still getting "Error attaching to volume. Volume: \Device\HarddiskVolumeShadowCopy60. Error: The specified request is not a valid operation for the target device" on the Hyper V hosts.

[foggy]

You can ask for confirmation from MS directly, but this seems to be known behavior: https://community.spiceworks.com/topic/ ... ter-backup

[Robvil]

Thanks.