Considerations for the virtual failover client location

Before setting up your virtual failover client (VFC), you must determine where it will reside. Supported VFC locations vary by Unitrends software version. For details, see Unitrends system requirements for WIR. The table below describes considerations for determining the VFC location.

Considerations

VFC on Recovery-Series appliance

VFC on external hypervisor

Unitrends system resources

VFC 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 retention

On 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 VFC

Use 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 clients

Cannot recover UEFI-based clients.

Supports recovery of UEFI-based clients.

GPT-partitioned clients

Cannot recover GPT-partitioned clients.

Supports recovery of GPT-partitioned clients.