VMware to Hyper-V - instant recovery limits

[mamosorre84]

Hello,

for a new project, we have to migrate 13k VM from VMware to Hyper-V.

Using Veeam instant recovery, what is the limit of parallel tasks that you have tested?

Any suggestion regarding hardware requirements?

Thank you

Marco S.

[Mildur]

Hi Marco

I reached out to our QA team to see if we have numbers.

Best,
Fabian

[Mildur]

Hi Marco,

I spoke with our QA team regarding your request.

In our tests, we typically run 25–30 Instant Recovery sessions simultaneously on Hyper-V. But that doesn't mean that you cannot run more.

Hardware requirements really depend on your specific environment, so there isn’t a universal answer.
When you initiate an Instant Recovery to Hyper-V, Veeam launches two agent processes: one on the backup repository and one on the target Hyper-V host:
- The repository agent’s memory and CPU needs depend on factors like backup size, chain length, block size, and whether encryption is enabled.
- On the Hyper-V host, the primary factor for RAM usage is the size of the virtual disk (VHD/VHDX) being restored.

Additionally, Veeam Backup & Replication will start a separate manager process on the backup server for each restore session, which also consumes memory and CPU resources.

As a best practice, we recommend not running more Instant Recovery sessions at once than the number of CPU cores on your Hyper-V host. Unfortunately, we currently don’t have formulas for estimating memory usage. Therefore I’d suggest starting with 5–10 IR sessions and monitoring how your hardware handles the load.

Best regards,
Fabian

[mamosorre84]

Hi Fabian, thank you for your well detailed answer.

I will keep these considerations in mind to plan the activities at best.

Marco S.