Considerations for the virtual failover client location


Pros and cons of the different locations of a virtual failover client.


Before setting up your virtual failover client (VFC), you must decide where it will reside.


ConsiderationsVFC on Recovery-Series applianceVFC on external hypervisor
Unitrends system resourcesVFC uses a portion of the Unitrends appliance’s processors, memory, and storage. This may impact the performance of regular system functions (such as backups, archiving, replication, deduplication, and purging). Monitor the appliance closely and make adjustments as necessary.VFC uses the hypervisor’s resources, and running the VFC does not impact performance of the Unitrends appliance. However, running the VFC can impact performance of the other VMs on the hypervisor.
On-system retentionOn system retention is reduced because a portion of the appliance’s storage is reserved for the VFC.VFC storage resides on the hypervisor. There is no impact on the appliance’s on-system retention.
Use case for the VFCUse temporarily until you can procure new hardware and perform bare metal recovery.Use temporarily or use the VFC VM to permanently replace the original Windows client.
UEFI-based clientsCannot recover UEFI- based clients.Supports recovery of UEFI-based clients.
GPT-partitioned clientsCannot recover GPT- partitioned clients.Supports recovery of GPT-partitioned clients.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us