Oftentimes, the configuration of the original client has changed or an incorrect IP address was used during setup.
Windows Instant Recovery (WIR) virtual failover client created on an ESX server is in a Halted state.
If it is determined an invalid IP address has been entered, the original client configuration changed, or a restore could not complete after three attempts, the virtual failover client must be setup again:
Delete the virtual failover client. Go to Recovery -- Instant Recovery, select the virtual failover client, and click "Tear Down". In the legacy UI, go to Settings -- Instant Recovery -- Windows, select the virtual failover client, and click "Delete".
If an incorrect IP address was entered, select a valid, unique IP address. Go through the steps to set up the virtual failover client again. For more information, see Windows Instant Recovery in the Administrator's Guide.
This applies to virtual failover clients on an ESX server when the virtual failover client is in the Halted state. Two possible causes are:
- For an existing client, the configuration of the original client has changed. The system has taken a new master backup and attempted to restore the virtual failover client.
- You assigned/entered an incorrect IP address when you created the virtual failover client. This IP address must be new and not in use by another system.
- Confirm the configuration of your original client has not changed and restores are successful. To do this, check the Windows Virtual Restores report for issues regarding configuration. Open the Unitrends UI and go to Reports -- Recover -- Recovery History or look at Reports -- Appliance -- Alerts Report. In the legacy UI, go to Reports -- Windows Virtual Restores Report.
- For a new virtual failover client set up on an ESX server with VMware, ensure a unique, unused, and valid IP address has been entered. Check the Alerts for a message about the virtual client under Reports -- Appliance -- Alerts. In the legacy UI, go to Reports -- Alerts.
- Review your network settings and ensure that your networking is correct.
- Make sure that your virtual failover client is available for restores.