How Windows instant recovery works

The diagram below illustrates a virtual failover client (VFC) running on a Recovery Series backup system. The appliance creates the VFC using system metadata acquired from an eligible backup or from the client itself. (See About retrieving configuration data for a virtual failover client.) After the VFC is created, it is continually updated with virtual restores of backups from the original client. (See Virtual restores for Windows instant recovery.) If the original client fails, you can boot the VFC in live mode and use it to temporarily replace the original client.

Because the VFC resides on the appliance, it uses the appliance’s resources such as processors, memory, and storage. A VFC cannot run on a Unitrends Backup appliance. To use WIR with a Unitrends Backup, you must run the VFC on an external hypervisor. For details, see Unitrends backup system managing a virtual failover client on an external hypervisor.

The diagram below illustrates a virtual failover client (VFC) running on a Recovery Series replication target. The replication target creates the VFC using system metadata acquired from replicated backups for the original client. After the VFC is created, it is continually updated with virtual restores of replicated backups from the original client. (See Virtual restores for Windows instant recovery.) If the original client fails, you can boot the VFC in live mode and use it to temporarily replace the original client.

Because the VFC resides on the appliance, it uses the appliance’s resources such as processors, memory, and storage. The backup system protecting the Windows client can be a Unitrends Backup or Recovery Series appliance. However, the replication target running the VFC must be a Recovery Series appliance. To create and manage a VFC from replicated backups on a Unitrends Backup, you must create the VFC on an external hypervisor. For details, see Unitrends replication target managing a virtual failover client on an external hypervisor.

The diagram below illustrates a Unitrends backup system managing a virtual failover client (VFC) on an external hypervisor. The appliance creates the VFC using system metadata acquired from an eligible backup or from the client itself. (For details, see About retrieving configuration data for a virtual failover client). After the VFC is created, it is continually updated with virtual restores of backups from the original client. (See Virtual restores for Windows instant recovery.)

If the original client fails, you can boot the VFC in live mode and use it to replace the original client. It can function as a temporary replacement until you recover the original client to new physical hardware. If the hypervisor has sufficient resources, the live VFC can replace the original client permanently.

Because the VFC resides on a hypervisor, it does not impact the appliance’s resources. It uses the hypervisor’s resources instead. The backup system managing the VFC can be a Recovery Series or Unitrends Backup appliance.

The diagram below illustrates a Unitrends replication target managing a virtual failover client (VFC) on an external hypervisor. The replication target creates the VFC using system metadata acquired from replicated backups for the original client. After the VFC is created, it is continually updated with virtual restores of replicated backups from the original client. (See Virtual restores for Windows instant recovery.)

If the original client fails, you can boot the VFC in live mode and use it to replace the original client. It can function as a temporary replacement until you recover the original client to new physical hardware. If the hypervisor has sufficient resources, the live VFC can replace the original client permanently.

Because the VFC resides on a hypervisor, it does not impact the appliance’s resources. It uses the hypervisor’s resources instead. The replication target managing the VFC can be a Recovery Series or Unitrends Backup appliance.