Virtual Standby Related
- During the Virtual Standby task, when you enable the Trusted Platform Module (TPM) device at the source node, the Virtual Standby VM in vSphere does not contain the TPM device. To add the TPM device manually, see Enable Virtual Trusted Platform Module for an Existing Virtual Machine.
- Virtual Standby does not support running VSB from VVol Datastore, due to limitation from VMware over Snapshot on VVOl datastore. For more information, refer to VMware link.
- Virtual Standby to EC2 does not support automatic starting of the Virtual Machine.
- Virtual Standby does not support Hyper-V cluster. If the Hyper-V cluster node name is used as the Virtual Standby destination, the Standby Virtual Machine is not added to the cluster view. The Virtual Standby job fails if the cluster node switch from the current Hyper-V host to other Hyper-V host.
- In VMware ESX Server environments that are configured in a Storage Area Network (SAN), the application copies only the first, full backup session to the ESX Server system using the SAN. For all subsequent full and incremental backups, the application copies the converted backup sessions using the LAN. The application behaves in this manner due to a VMware limitation. For more information, see the VMware website.
- Due to a VMware limitation, Virtual Standby cannot create virtual machines on ESXi Server systems using a free license. To create virtual machines, you need to buy a license.
- Due to a known VMware limitation, errors in the Activity Log appear in English when the Location is set to a non-English locale.
- The Virtual Standby VM does not support Microsoft Cluster node with Cluster Shared Disk as source node.
- Note: The Cluster Shared Disk status is offline after the Virtual Standby VM boot up.
- Install the system volume on the first disk. Verify that the system volume and boot volume of the source machine are on the same disk.
- Note: This limitation is only for VSB to cloud.
- The maximum hard disk storage supported for virtual standby to VMware is 62 TB.
- For more information, refer KB Article.
- The maximum hard disk storage supported for virtual standby to Hyper-V is 64 TB.
- For more information, refer link.
- Due to a Hyper-V limitation, Virtual Standby cannot support the UEFI system. The limitation prevents supporting a virtual machine that uses the Unified Extensible Firmware Interface (UEFI). Therefore, deployment fails when you deploy a Virtual Standby task, whose Standby destination is Hyper-V Server, to a UEFI system. This scenario is applicable to the Hyper-V Server 2008, 2008 R2 or 2012.
- Note: If the destination Hyper-V Server version is 2012 R2 or above, verify the following Microsoft documentation for the supported UEFI system for guest OS boot: