Problem with a VM (Migrated from Hyper-V)

[stefanbrun]

Hi,

Case: 01244187

we have a Problem with a Server 2012R2 VM that was on Hyper-V and now on VMware.
The VM was migrated without uninstalling the Integration Services. Now we have Problem with the VSS Provider --> Hyper-V IC Software Shadows Copy Provider.
Can't Backup the VM with Veeam B&R.

I know that the uninstallation would be possible if we have the ISO from the Hyper-V Host, but the Hyper-V Host is deleted = no ISO.

I have also postet a Topic to Microsoft --> https://social.technet.microsoft.com/Fo ... rverhyperv

Somebody has an Idea or the specific Server2012R2 ISO --> vmguest.iso?

[veremin]

I'm wondering whether the backup fails as a whole or it's just Application Aware Image Processing that doesn't work. Also, have you seen this workaround (though, described for Windows 7 VM)? Thanks.

[stefanbrun]

yeah see that workaround but, i didn't have any Backup. So im searching another way.

The Backup fails as a whole...

05.01.2016 01:48:11 :: Failed to prepare guest for hot backup. Error: VSSControl: -2147212529 Backup job failed.
Discovery phase failed.
Cannot add volumes to the snapshot set.
Cannot add a volume to the snapshot set. Volume name: [\\?\Volume{0c69b76c-ebcf-11e3-80b5-806e6f6e6963}\].
Cannot add volume to the set of volumes that should be shadowed.
VSS error: VSS_E_UNEXPECTED_PROVIDER_ERROR. Code:0x8004230f

[veremin]

Failed to prepare guest for hot backup

It's AAIP error. I think both AAIP and "require successful processing" options are enabled, thus, backup fails as a whole. Try to disable them and proceed with a backup, then, try the proposed workaround. Thanks.

[stefanbrun]

Yes with "Try application processing, but ignore failures" the VM will be processd.
I will check with the workaround.

[veremin]

Yep, now with a successful backup you can start experimenting with workarounds. Kindly, keep us updated on the results of your findings.

[Alec King]

If the VM was migrated from Hyper-V to VMware, has the Hyper-V VSS provider been removed?
You can check using command

Code: Select all

vssadmin list providers

If you see "Hyper-V IC Software Shadow Copy Provider" in the list, then it could be causing problems with VSS.

You can delete the registry key that references this provider -

Code: Select all

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{74600e39-7dc5-4567-a03b-f091d6c7b092}]
@="Hyper-V IC Software Shadow Copy Provider"
"Type"=dword:00000002
"Version"="1.0.0.0"
"VersionId"="{c797fff9-2c3e-453c-a3e9-cc7673a6c732}"

The details are in this post http://forums.veeam.com/microsoft-hyper ... 21720.html

Of course all the usual warning about modifying the registry would apply! Backup the VM, and the registry, before making any changes.

Let us know how it goes.

[ahodzic]

Deleting registry key "Hyper-V IC Software Shadow Copy Provider" worked for me. Thank you!