Live mode recommendations for a virtual failover client running on an external hypervisor

If the virtual failover client (VFC) will replace the original client only temporarily, you should recover the client to new hardware as soon as possible using Unitrends bare metal recovery, as described in Windows Bare Metal Protection. Data from the live VFC is protected by the backup schedule for the original client, and you will need to restore it after recovering the client to new hardware. For details, see Restore Overview. After restoring the VFC’s data to the recovered client, you should delete the VFC from the appliance and the hypervisor. For instructions, see Deleting a virtual failover client.

If the virtual failover client (VFC) on a hypervisor will permanently replace the original client, you should determine whether you wish to continue protecting the VFC with the backup schedules for the original client or whether you prefer to run Hyper-V or VMware backups for the VM, depending on its location. For details about backups, see Backups Overview.

Note:  It could take several minutes for a live VFC on a hypervisor to show up in the list of VMs to protect with VMware/Hyper-V backups. The VFC is not automatically added to a VM backup schedule.

You should then delete the VFC’s information from the appliance that was managing it. For instructions, see Deleting a virtual failover client. Be sure to delete the VFC from the appliance only, as you have the option to delete it from the hypervisor as well.