SecondSite Hyper-V Considerations

Owned by Tahir Kulelija
Last updated: 03 Dec 2020
2 min read

Zettagrid operates a VMware based Zerto environment. Please note that there are some special service considerations that need to be verified to achieve a successful SecondSite replication service when using Hyper-V at the customer site:

Considerations

  • When recovering from Hyper-V to VMware, the virtual machines are recovered with the same number of sockets as CPUs and not the original number of sockets.
  • When protecting Windows 2012 R2 virtual machines from Hyper-V to VMware, after a failover test you may need to reactivate the virtual machine.
  • When recovering Windows 2008 virtual machines from Hyper-V to VMware, at start-up the recovered virtual machine guest operating systems request System Recovery.
    Workaround: Before attempting recovery operations, update the guest OS registry in Windows 2008 virtual machines as follows:
    a) Create a blank .reg file.
    b) Copy the following text to the new .reg file:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS] ?Start?=dword:00000000
    c) Copy the .reg file to the protected virtual machines in Hyper-V.
    d) Double-click the file and click Yes to confirm the change.
    e) Delete the .reg file that you copied to the protected virtual machines.
    The virtual machines will now start successfully for all recovery operations to VMware. For more details, see VMware KB #1005208.
  • Zerto Virtual Replication script parameters use vSphere terminology, even for scripts in a Microsoft Hyper-V environment.
  • Re-IP does not work for Linux machines.
  • During a storage disaster, if the VRA is shutdown and restarted after the storage is recovered, the journal and recovery volumes managed by the VRA may be deleted.
  • In Change VM Recovery VRA, via MORE in the VRAs tab under SETUP, the values in the column VM Size (GB) are not correct.
  • Changing the storage used by a VRA from a CSV to non-CSV storage, or from a non-CSV storage to CSV storage, fails.
  • You cannot protect virtual machines using storage that is only configured in Hyper-V and not in SCVMM.
  • Virtual machines with fixed size disks are always recovered with dynamically expanding disks.
  • VSS checkpoints are only implemented when protecting Windows 2012 generation 2 virtual machines.
  • Protected virtual machines must have the latest version of Integration Services installed in order for a re-IP to be successfully performed.
  • SCVMM is not automatically refreshed after any recovery operations to or from the SCVMM. This can result in Integration Services not being detected by the Zerto Virtual Manager and this can lead to virtual machines failing to boot and Integration Services functions such as re-IP not working.
    Workaround: Manually refresh SCVMM.
  • All management operations that can be executed from SCVMM, must be executed from SCVMM and not from the HyperV host. For example, removing a virtual machine must be done from the SCVMM console and not from the Hyper-V console.
  • Removing a virtual machine from a VPG is not reflected in the user interface.
    Workaround: Re-edit the VPG to remove the virtual machine and click DONE.
  • A VRA cannot be installed on a Hyper-V host when the host is attached to a LUN via iSCSI along with other Hyper-V hosts.
  • In order to reconfigure the SCVMM credentials via the Diagnostics utility, you must first stop the Zerto Virtual Manager.
  • A protected virtual machine defined in the VPG to have a static IP address on recovery will switch to a DHCP configuration when recovering.