Hi, I may have found the answer to my question on this link but I was wanting to check this answer is still valid with the current versions.
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/605c2a56-3253-4618-8e8b-e11fd51f5392
I have a Hyper-V 2012 Cluster setup with a 2012 Shared SMB File Server. I have configured SCVMM 2012 SP1 (released in Dec) and alse used Cluster Manager to check the quorum settings as I cant find that bit in SCVMM yet for SMB storage.
I have 2 HA 2012 Servers running on Host1 and I pull the power (or remove network cables) and the VMs fail over to Host2. However the VMs actually reboot during this move instead of live migration. In the earlier post from 2010 Elden Christensen explaines it quite well and states that this is the correct procedure for hosts to move to a new node after a node failure.
My question is, is this still true with the current software I am running or have I done something wrong in my installation.
I am planning to run both Windows and Linux VMs on this including Exchange Server. Would I expect the same issues on these VMs like FSCK checking on disks after a failover, like what you might experiance on a physical power failure on a linux server. Or is there some nice virtual disk technology inside Hyper-V that keeps the disks safe on the shared storage and the VM reboot is just like booting after a normal shutdown with less risk.
Sorry for the vague questions, but the clustering side is quite new to me and I would like as much reassurance as possible.
We will be running Replications to another HyperV DAS Server (or possibly another cluster) and from what I have read, its best to take normal backups of the exchange databases as vss snapshots are not guaranteed for databases.
Thanks for any help or advice,
Dave