Restores for the virtual failover client on an external hypervisor are not running

If restores for a virtual failover client (VFC) residing on an external hypervisor are not running, this problem could be caused by one of the following:

     Virtual restores are not enabled for the VFC. For details, see Virtual restores are not enabled for the virtual failover client.

     The Unitrends appliance cannot communicate with the VFC. For details, see The Unitrends appliance cannot communicate with the virtual failover client.

     Configuration changes have been made to the original client. For details, see Configuration changes have been made to the original client.

     The VFC has been booted in live mode. For details, see The virtual failover client has been booted in live mode.

Virtual restores are not enabled for the virtual failover client

To determine whether virtual restores are enabled, view the virtual failover client (VFC) details in the managing Unitrends appliance by selecting Settings > Instant Recovery > Windows. If restores are enabled, a yellow light bulb displays in the Enabled column. If the light bulb is dark, restores are not enabled.

You can enable restores using the procedure described below:

To enable virtual restores for a virtual failover client

1        Log in the Unitrends appliance managing the VFC, and select Settings > Instant Recovery > Windows.

2        Click the line of the VFC you want to modify. You see the Modify Virtual Failover Client window.

3        Check the box next to Enable virtual restores to the failover client.

4        Click Confirm.

Backups that completed while restores were disabled are now restored to the VFC.

The Unitrends appliance cannot communicate with the virtual failover client

The appliance cannot perform virtual restores if it cannot communicate with the virtual failover client. After the first failed attempt to perform a restore, the appliance places the VFC in a Halted state. After several minutes, it attempts the restore again. After three failed attempts, the status of the VFC becomes Invalid, and it remains in a halted state until you delete it.

The most likely reason the appliance cannot communicate with the VFC is that there is a problem with the network settings. To resolve this problem, you must delete the VFC (see Deleting a virtual failover client) and create a new one with valid network settings (see Creating a virtual failover client).

When assigning network settings to the new VFC, consider the following:

     The IP address must be unique.

     The IP address must have the same subnet as the hypervisor on which the VFC resides.

     You must assign the VFC the same gateway as the hypervisor on which the VFC resides.

Configuration changes have been made to the original client

Restores to the virtual failover client (VFC) fail if the configuration of the original client has been changed (for example, a disk has been added or removed). After the client’s configuration has changed, the next virtual restore to the VFC for the client fails, the status of the VFC becomes Invalid, and it remains in a Halted state until you delete it from the appliance. To resolve this problem, you must delete the VFC (see Deleting a virtual failover client) and create a new one (see Creating a virtual failover client).

The virtual failover client has been booted in live mode

After a virtual failover client has been booted in live mode, its status is Invalid, it is no longer manged by the appliance, and virtual restores are no longer performed. For details, see Taking a virtual failover client live. If you no longer need the VFC to run in live mode, and you would like to create a new VFC for the client, you should first delete the existing VFC (see Deleting a virtual failover client) and then create a new one (see Creating a virtual failover client).