Hi everyone, I have set up 2 Hyper-V servers in a Failover Cluster. After testing a few failover scenarios, I have a few questions. When I made the VM (running on node 1) to crash (blue screen), it took approximately 4 minutes for node 2 to take over the VM. And the VM appeared in a rebooted state in node 2, in which it did not retain any application instance/state that it had when it was running in node 1. Is this normal behaviour for a Failover clustering configuration? Can I reduce the time it takes to detect a failover? Is there a Hyper-V application level failover? For example, if it detects that one of the applications (not Windows services) is not running or is hanging, it will start that application. If so, is this an API integration or Hyper-V configuration will do? Thanks. YH

Hyper-V High Availability

Yih Hung Tan 1

Hi everyone,

I have set up 2 Hyper-V servers in a Failover Cluster. After testing a few failover scenarios, I have a few questions.

When I made the VM (running on node 1) to crash (blue screen), it took approximately 4 minutes for node 2 to take over the VM. And the VM appeared in a rebooted state in node 2, in which it did not retain any application instance/state that it had when it was running in node 1. Is this normal behaviour for a Failover clustering configuration? Can I reduce the time it takes to detect a failover?
Is there a Hyper-V application level failover? For example, if it detects that one of the applications (not Windows services) is not running or is hanging, it will start that application. If so, is this an API integration or Hyper-V configuration will do?

Thanks.
YH