[Feature request] restore vm files (vhd or vhdx) for multiple VMs at once

[kunniyoor]

Need to have option to restore vm files (vhd or vhdx) for multiple VMs from a single backup (per VM) sets.

Currently if we are having multiple VMs which are backed up in a single backup set (per VM) and to restore two or three VMs virtual disk we have to run that no.of restore jobs. its tedious task when we need to restore the virtual disks of 10 - 20 VMs.

[foggy]

Thanks for the request, noted. Could you please describe the scenario where you need to restore some VM files/disks for multiple VMs at once instead of restoring the entire VMs?

[kunniyoor]

We were enabling replication for production hyper-v VMs to DR site. Initial replication failed with check point creation failed error. But even though the job failed, it created replica vm in DR hyper-v without virtual disk.

So we need to execute below workaround inorder to run the replication successfully.

Initiated the replication by enabling replica seed as usual.
. Got said Error after a while. but the job created replica VM with out any virtual disk in the target cluster (windows 2019).
. Modified the replica VM setting and enabled "Production Checkpoint" option.
. Restored the virtual disk and attached to the replica VM.
. Rerun the replication and it got created the replica VM successfully.

So to restore the virtual disk of 15 replica VM in the DR server, we have no other options other than runing the restore job 15 times to restore individual virtual disk of each VM. Most important that all VMs were backed by a single job with per VM backup set.

[foggy]

Well, in that case I'd rather investigate the check point creation failure.

[kunniyoor]

We'd case already going on with support for the that issue in the first place Case # 04285270. Production 2016 and 2012 hyper-v VMs are able to backup and replicate locally with out enabling "Production checkpoint". We are facing issue while replicating other ses of production hyper-v VMs to new DR site (2019 hyper-v). We are short of time to setup the DR as in a span of 3 days its should go live.

So we don't have any other option other than the above steps.

Krish

[foggy]

Got it, thanks.