Restarting the only working node in a Hyper-V Failover Cluster
I have created a 2012 R2 Hyper-V Failover Cluster intented for 2 nodes that only has one node at the moment based off HBAs and a Fiber storage backend.
When this onlyy active node is restarted the storage is not ready when Hyper-V initiate Virtual Machine startup - hence they are left in a Off-Critical state. Whats worse is that human intervention is required to start the VMs.
Any suggestions as to how do I solve this problem?
When this onlyy active node is restarted the storage is not ready when Hyper-V initiate Virtual Machine startup - hence they are left in a Off-Critical state. Whats worse is that human intervention is required to start the VMs.
Any suggestions as to how do I solve this problem?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks again!
ASKER
VB ITS:
As I see it, this is a means to control in which order Windows Roles come online on a Hyper-V Host, not to avoid that the storage system is not ready when the Cluster is.
Philip Elder:
As I understand you, you also see the need to control the time (pause) before a virtualization host GENERALLY begins initializating VMs.
I am not sure though whether you say that you've made your own solution to remediate the lack of a builtin solution?
Thanks!