VRO - Hyper-V - Recovery Steps

[MikeD82]

Does Hyper-V in VRO support custom steps? Seems like I only have 4 steps available in a recovery plan.

[Alec King]

Hi, Currently recovery to Hyper-V does not support injection of custom scripts into the restored VM. However you can still run custom scripts that execute on the Veeam Backup server, or the Orchestrator server.

[MikeD82]

Is this on the roadmap? I would like to change the IP address during a recovery.

Thank you.

[dali@iae.nl]

I do miss those steps also for Hyper-V in VRO.
VRO for Hyper-V is far from complete. In my opinion it now is a sort of beta product until it can recover from Hyper-V Checkpoints (that are Hyper-V "Snapshots"). Of course you can recover from Backups instead of Checkpoints but in most cases that will take too long if you have many TB's. Veeam says there is nothing on the roadmap for that.

[jklaw91]

My company also very much needs this. We recently migrated from VMware to HyperV and are struggling with loss of features on several Veeam products, including this one. Thx

[Alec King]

Hi all,

We are actively researching how to bring Hyper-V support in VRO to feature parity with VBR core capabilities.

In fact we just shipped VRO 13.1 where we added two big Hyper-V features - restore to Azure, and use of a single host in a Recovery Location. And more features are planned!

For some more advanced integrations such as running custom scripts inside VMs, and support for Datalabs, we are (re)building integrations to support that right now.

If you do have specific requests, please post them here, we can investigate possible workarounds.

@dali@iae.nl RE: revert a Hyper-V checkpoint. Do you want to revert to 'most recent'? Of course a selection from all checkpoints would be ideal, as we do for restore points, but what do you require as a minimum viable feature? We can execute commands on the Hyper-V host, so if we can pass the relevant parameters it could be possible.

@@MikeD82 RE: Change IP address. This could also be possible via commands run on the host. If you share the logic of re-IP scheme I will look into the connection part.

Thanks!

[dali@iae.nl]

In Fact we want to Recover from Replica. So the Replica is already at the other site. Only the procedure to update them and failover.
Now in VRO for Hyper-V only possibility is to recover from backup (= complete restore), not from Replicas.

Of course we can do manualy Failover to replicas as workaround since VRO cannot do that.
But ... we have Replica Jobs which do replicate many VM's in parallel. When doing Failover for many VMs Veeam process them serial which takes hours and hours. At the moment we do a workaround by 1. But down the VM's which has to failover. 2. Run the Replica Jobs. 3. Start the VMs on the other site.
Veeam has to solve this "issue" so VMs will failover to replica's in parallel.

I should love to be a tester for all that new features in our Hyper-V (in our case Azure Stack HCI, what is in the name ...).