Article number
000004326
Affected Versions
All
Source Hypervisor
All
Target Hypervisor
All
Failover Test failed due to CDROM first on boot order
Viewed 282 times
Summary
One or more VMs in the failed over VPG has CDROM drive set as first in boot order configuration of the VM.
Zerto in general does not support failing over CDROM drives in the failed over VMs.
Please note: If in the failed over VMs the CDROM drive will be set not as first in boot order, the FOT will succeed but the machines will be failed over without the CDROM drive. FOT for a VPG will fail with the following error:
Zerto:Protection group failover test. Failure.
Failed: VM DATA01 - testing recovery could not
be created Message: A specified parameter was
not correct. configSpec.bootOptions.bootOrder.
Fault: Vim25Api.InvalidArgument.
Zerto in general does not support failing over CDROM drives in the failed over VMs.
Please note: If in the failed over VMs the CDROM drive will be set not as first in boot order, the FOT will succeed but the machines will be failed over without the CDROM drive. FOT for a VPG will fail with the following error:
Zerto:Protection group failover test. Failure.
Failed: VM DATA01 - testing recovery could not
be created Message: A specified parameter was
not correct. configSpec.bootOptions.bootOrder.
Fault: Vim25Api.InvalidArgument.
Steps
Remove the CDROM drives from VM boot order configuration.
In order to do so, please refer to the following VMWare and Microsoft KBs respectively:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2011654
https://blogs.technet.microsoft.com/jhoward/2013/10/25/hyper-v-generation-2-virtual-machines-part-2/