Instant recovery to Hyper-V - case ID #05920513

[tpayne]

I have had a server 2019 Hyper-V instance for a few releases of Veeam (lets call it Hyper-V A) and have had success with instant VM recovery and Migrate to Production for a restore workflow. It has various iSCSI volumes for its production VM storage. I recently added another server configured identically as far as networking and iSCSI storage backing (Lets call this Hyper-V B). On the new server only, when I "Migrate to Production" after the Instant-Recovery finishes, the VM will crash and not find a boot device immediately after the "Merge Checkpoint" Process in Hyper-V completes. there are Zero Errors on the Hyper-V B server. Both Veeam and Hyper-V show all the tasks completing successfully.

I took an iSCSI LUN where the operation worked on Hyper-V A, remapped it to Hyper-V B from the SAN and tried the same operation and it still failed. Hyper-V B started as a server 2022 core. For troubleshooting i re-installed windows to match Hyper-V A (server 2019 with GUI) and it did not fix the issue.

Has anyone had issues with Instant VM recovery to Hyper-V on recent deployments? I wonder if the way Veeam deploys the transport services has changed? I have tried turning off windows defender, disabling TPM from the BIOS. Hyper-V A and Hyper-V B are the same type of Dell server (PowerEdge R640) with slightly different CPUs.

Another odd wrinkle to this case, is that the process works fine if I pick the C drive on Hyper-V B as the destination instead of the iSCSI volume.

I have a Veeam case open on this (#05920513) and I've been told to open a Microsoft case, but as Microsoft doesn't have a tool that works the same way as instant recovery, I am not sure what to tell them without bringing up a 3rd party software. I have tested the Move feature in Hyper-V and have had no problems. My next step is setting up a Microsoft case and get a conference call with Veeam support.

Any insight would be appreciated.

[Mildur]

Hi Tim

Has anyone had issues with Instant VM recovery to Hyper-V on recent deployments?

I checked our recent support cases and couldn't find similar issues.

I don't recall any changes which affects deploying our transport service in V11.
My suggestion is to keep working with support. Guessing a solution over the forum is not possible.
I would ask Microsoft support to check the configuration of the migrated VM. Microsoft also may help you in analyzing memory dumps of the bluescreen. Those dumps should help to explain why this blue screen has happened.

As a workaround, you could try to export the disks as VHDX files with Veeam V12 and copy them manually to the HyperV iSCSI drive: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian