What restrictions are there when performing replication from Hyper-V to VMware using Zerto?
Are there any documents that list restrictions?
Brian from Zerto here.
There are many considerations for each hypervisor installation, please go over our Installation guide Page 7 & 8 where the requirements and considerations are listed. http://s3.amazonaws.com/zertodownload_docs/6.5_Latest/Zerto%20Virtual%20Replication%20Installation%20Guide%20for%20vSphere%20and%20Hyper-V.pdf
Also, please go over our interoperability matrix to check versions and features limitations: http://s3.amazonaws.com/zertodownload_docs/Latest/Zerto%20Virtual%20Replication%20Operability%20Matrix.pdf
If you have a specific limitation you are worried about, due let us know.
For example, is there a case where the virtual machine configuration has changed after Zerto failover or Move?
For example, in my customer, when moving a virtual machine from Hyper-V to VMware with Move, the order of drives other than the C drive may be switched.
Is there any change in the configuration of the original VM except in the case where the order of the disks is changed?
The disk order change is probably due to a requirement in VMware environment.
A source VM might not have any disk attached to SCSI controller 0 at node 0:0.
However, VMware requires that when a new VM is created, there should be a disk attached to the position.
When failover, the first disk in order on the recovery site will be attached to SCSI controller 0 at node 0:0.
This makes the failed-over VM has a different disk order from the source VM.
If any questions, please feel free to let us know.
Thank you for information.
I understood the problem on the vSphere side.
We have been asked by customers that if VMs are migrated from Hyper-V to VMware, the settings may differ from the original VM configuration.
Please let us know if there is any case on the Zerto side.