?
Solved

Hyper-V VMs failing

Posted on 2014-01-28
12
Medium Priority
?
224 Views
Last Modified: 2014-11-12
We have 2 Hyper-V server that have been having some issues with failover.  From what I can gather the failure is because of my first Hyper-V host.  

Everything seems to depends on him.  When he goes down so does everything.  When I check the second Hyper-V host he cannot see any of the volumes to boot the VMs.  But, once the first host comes up he then can see them.

Now we have our two hosts setup in a Quorum Config of Node and Disk Majority, but for whatever reason if we lose the first host, we still lose all our VMs.

Any ideas?
0
Comment
Question by:Computech
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 4
12 Comments
 
LVL 7

Expert Comment

by:Ned Ramsay
ID: 39815584
This may sound really stupid (I dont know your level of knowledge) but are the the volumes actually attached to the first host so when it goes down it stops providing ISCSI to the second? Ive seen people misconfigure storage in this way.
0
 

Author Comment

by:Computech
ID: 39815601
I have my CSVs attached through ISCSI to both hosts.  But in checking things out today, I only see the CSVs on the first host's disk manager and not on the second host.  Yet I can access the volumes in Explorer on both hosts.

I'll admit, I'm not a Hyper-V guy but a VMware guy so I'm not going to play like the expert when it comes to this.  So feel free to say what you are feeling!!
0
 
LVL 59

Expert Comment

by:Cliff Galiher
ID: 39815618
Sounds like your witness disk doesn't have a direct path to your second node. Have you made any recent changes and did you revalidate the configuration?
0
Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

 

Author Comment

by:Computech
ID: 39815658
We had some backup software that screwed with things a while back and we removed it a while ago as we ran into this same issue.  Do I need to revalidate the configuration everytime I make a change?  Is that the same as Validating the Cluster?  I've ran it, but excluded the volumes as it said that it would take down the volumes and I don't want to do that!
0
 
LVL 59

Expert Comment

by:Cliff Galiher
ID: 39815663
If you make changes to the fluster itself then yes, you really should revalidate.
0
 

Author Comment

by:Computech
ID: 39815779
Will it really take down my volumes and kill my VMs if I do the validation?
0
 
LVL 59

Expert Comment

by:Cliff Galiher
ID: 39815809
The logic here is that you can either interrupt service in an orderly way during a maintenance window, or you can have service interrupted when node 1 fails and node 2 doesn't take over... which apparently has happened to you once already to discover the problem.

So it isn't a matter of 100% uptime, but when and how you want that downtime to occur. As always, have backups! If your cluster is not stable,  the process indeed could make things worse.
0
 

Author Comment

by:Computech
ID: 39815886
I'm just trying to evaluate if I can run the validation on the disks right now or if I should scheduled a time when I can.

Having said that, do you think the validation will correct the error or tell me what the problem is?
0
 
LVL 59

Expert Comment

by:Cliff Galiher
ID: 39815907
That's what the validation tool is designed to do. Of course, of things are too far out of whack, it may not be able to. In such cases, rebuilding the cluster is easier.
0
 

Author Comment

by:Computech
ID: 39816004
Sweet, well then I'll see what I can do tonight and go from there.
0
 

Accepted Solution

by:
Computech earned 0 total points
ID: 39836365
Okay, so we figured out what was going on.  Apparently both hosts should see all the volumes.  So, we found out it was an issue with the ISCSI initiator on the server.  Once we disconnected the ISCSI and reconnected it then the volumes were seen and everything started working again.
0
 

Author Closing Comment

by:Computech
ID: 39882033
We were able to find a solution to the issues without following the instructions provided on this question.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
In previous parts of this Nano Server deployment series, we learned how to create, deploy and configure Nano Server as a Hyper-V host. In this part, we will look for a clustering option. We will create a Hyper-V cluster of 3 Nano Server host nodes w…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question